<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by AJ Dyer on Medium]]></title>
        <description><![CDATA[Stories by AJ Dyer on Medium]]></description>
        <link>https://medium.com/@ajdyer?source=rss-a0cf28d08eef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JFluAjfMr513keyFam0UQg.jpeg</url>
            <title>Stories by AJ Dyer on Medium</title>
            <link>https://medium.com/@ajdyer?source=rss-a0cf28d08eef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:08:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajdyer/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Ansible for IBM Z User Spotlight Series: Stewart Francis]]></title>
            <link>https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-stewart-francis-dd60c489a82d?source=rss-a0cf28d08eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd60c489a82d</guid>
            <category><![CDATA[ibm-z]]></category>
            <category><![CDATA[mainframe-modernization]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[AJ Dyer]]></dc:creator>
            <pubDate>Fri, 27 Dec 2024 14:45:26 GMT</pubDate>
            <atom:updated>2026-03-23T21:52:01.411Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this series, we shine a light on the people who make the Ansible</em>®<em> for IBM</em>®<em> Z</em>®<em> community thrive. We share the inspiring stories of users who combine experience, skill, and curiosity to shape strategies, influence organizations, and take our tools to new heights.</em></p><figure><img alt="This is an image of the Ansible for IBM Z User Spotlight Series Banner" src="https://cdn-images-1.medium.com/max/1024/1*aCBm4D5VT5PxB101-ER_Uw.png" /></figure><h4>Getting to know Stew Francis</h4><p><em>Stew Francis joined IBM after graduating from Cambridge University in 2003. Working from the Hursley Park location of IBM, he currently leads the CICS</em>®<em> TS Modernization team in a technical capacity. Stew and his team focus on improving multiple aspects of the developer experience. He regularly attends conferences to share exciting news and valuable insights on using Ansible, z/OS, and the CICS Transaction Server (TS) collection.</em></p><figure><img alt="This is an image of the featured Ansible for IBM Z series user: Stewart Francis." src="https://cdn-images-1.medium.com/max/1024/1*jgA9r6oQLhPvzlmLj0T5hg.png" /></figure><h4>How did you get started with Ansible?</h4><p>I joined IBM right out of university and spent most of my time working with <a href="https://www.ibm.com/products/cics-transaction-server">CICS</a>. I started as a junior developer working on CICS Explorer®, which is our graphical system administration console. I eventually became the lead developer and subsequently head of the Developer Experience Modernization team. Since then, I’ve been involved with modernizing the Java development toolchain of CICS and most recently with Ansible integration for CICS TS.</p><blockquote><strong>“Ansible has streamlined provisioning tasks significantly, offering broad functionality.”</strong></blockquote><h4>Why Ansible?</h4><p>CICS has a powerful REST API that drives the data and interactions you can use to manage your CICS regions. We created an Ansible collection to see if we could make it easy to call that API with Ansible, which would be a nice fit for lots of workflows based on Ansible. The ability to manage the state of your CICS region through Ansible workflows was a big part of the motivation.</p><h4>What benefits has Ansible brought to your team and how usable has it been?</h4><p>Our team is responsible for several CICS environments, and we use our Ansible collections to manage those. Ansible has streamlined provisioning tasks significantly, offering broad functionality. Despite the team being new to z/OS, new team members found that Ansible’s relatability and compatibility with Python was highly beneficial because it allowed the team to contribute effectively to collection enhancement, especially with tools like Microsoft Visual Studio® and the Red Hat® Ansible extension, which facilitates quick onboarding and ease of use.</p><blockquote><strong>“Ansible is extensible and relatively unopinionated, so you can use it to drive existing system automations…or bring all things together into a single automation.”</strong></blockquote><h4>In your view, how does Ansible measure up to other modernization technologies?</h4><p>Ansible is popular and has a lot of momentum because of its success on other platforms. The technology is powerful, and the Red Hat <a href="https://www.redhat.com/en/technologies/management/ansible">Ansible Automation Platform</a> brings additional capabilities. The available collections — whether they’re hosted on <a href="https://galaxy.ansible.com/ui/">Galaxy</a> or the <a href="https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/auth?client_id=cloud-services&amp;redirect_uri=https%3A%2F%2Fconsole.redhat.com%2F&amp;response_type=code&amp;scope=openid&amp;nonce=ccc3e231-b076-4b1e-977a-82776dc8619a&amp;state=3a066a33d03e459fa6ffad7d10a3aa4f&amp;response_mode=fragment">Automation Hub</a> — bring great out-of-the-box support. That all works in Ansible’s favor.</p><h4>Was there a moment when you really grasped the potential of Ansible that proved correct?</h4><p>We have a CICS region with quite old pieces of automation made from REXX (Restructured Extended Executor) and JCL (Job Control Language) that we use each time we create an instance or change a configuration. We built a replacement automation with Ansible. Both automations achieve the same task, but the quality of the result and the overall experience are much better with Ansible.</p><p>Similarly, when we started using the Ansible Automation Platform to manage our development systems, we moved from a world where each user must check their system for changes and run upgrades manually to one where we can update each user’s system automatically. That’s not difficult with Ansible, and it’s great to provide a service rather than tell people that they have a chore to do.</p><h4><strong><em>How well does Ansible fit into existing information flows?</em></strong></h4><p>Many of our client conversations are around how Ansible fits within their existing automation landscape. That use case highlights Ansible’s strengths — you can use it for raw automation, but you can also use it as a kind of automation integration fabric. Ansible is extensible and relatively unopinionated, so you can use it to drive existing system automation or z/OSMF (z/OS® Management Facility) processes, call a piece of JCL, execute a bit of REXX, run a Python automation script, or bring all things together into a single automation. You can then surface the result in the Red Hat Ansible Automation Platform to make it available to everyone.</p><h4><strong><em>Why use Ansible over other z/OS automation tools?</em></strong></h4><p>There has never been a case where Ansible has not been a good fit to solve automation problems. If I have a process with a lot of manual components, I always feel like I can use Ansible to handle the low-level building blocks, particularly with the features available in the <a href="https://github.com/ansible-collections/ibm_zos_core">z/OS® core collection</a>. The built-in templating support, conditional processing, and playbooks make it quite adaptable to fit those niches. To get a feel for Ansible, it’s often just a case of working hands-on with its capabilities, getting familiar with the z/OS core collection, and trying to automate a few things.</p><p>The Ansible approach to automation is different from that of other tools on the Z platform, but when I talk to clients, I find that many already have Red Hat Ansible Automation Platform deployed somewhere in their organization, so it can be quite a short journey to develop automation and make it accessible to their colleagues as a service. This makes it easy for them to realize value from that automation.</p><figure><img alt="This is an image of Stewart Francis presenting at the SHARE conference in 2024" src="https://cdn-images-1.medium.com/max/1024/1*hOSYwi_AVSayNErD9VNwSQ.png" /><figcaption>Stewart Francis presenting at SHARE 2024</figcaption></figure><h4><strong><em>Tell us about the Ansible 101 presentation you recently gave at SHARE in Kansas City and its major takeaways.</em></strong></h4><p>We often present Ansible from a CICS perspective, but we also show what you can do with Ansible in general. We’ve added lots of new things to the CICS TS collection, so this time around we couldn’t cover both topics in one presentation. We ended up doing two: one focused on CICS TS and an <em>Ansible 101 </em>session to help people get started. The introductory session was very well attended — we even ran out of chairs.</p><p>This session highlighted how Ansible’s architecture differs from traditional automation systems, especially z/OS environments, making it essential to understand the conceptual model of its architecture. The control node — an ephemeral orchestrator that can be any system capable of running Ansible — initiates automation on the managed node (z/OS) via SSH and terminates after completion. The transient, non-persistent nature of the control node is a paradigm shift, offering flexibility and scalability but requiring a mental adjustment for those used to traditional, persistent automation systems.</p><blockquote><strong>“Ansible is a great technology to help us start adopting configuration as code patterns, which could include emulated z/OS environments as well</strong>.”</blockquote><h4><strong><em>The IBM z/OS CICS collection is a prominent part of the </em></strong><a href="https://www.ibm.com/support/z-content-solutions/ansible/"><strong><em>Red Hat Ansible Certified Content for IBM Z</em></strong></a>®<strong><em> offering.</em></strong> <strong><em>What are some of its popular use cases?</em></strong></h4><p>If you’re doing repetitive tasks in CICS Explorer, our modules — in conjunction with the Ansible platform — essentially form a nice scripting environment that you can use to automate those tasks. Whether it’s grabbing data from your system to compose a report, defining new transactions, or changing your system topology to add a new routing or application region, you can write an Ansible playbook that is quite powerful.</p><h4><strong><em>Do you see further investment in this collection?</em></strong></h4><p>Typically, CICS provisioning involves running JCL jobs and following a traditional configuration process. We now have a collection of Ansible modules that help you provision CICS regions from scratch. If you have <a href="https://www.ibm.com/products/z-open-automation-utilities?mhsrc=ibmsearch_a&amp;mhq=z%2520open%2520automation%2520utilities">ZOAU</a> (Z Open Automation Utilities) up and running, you can use a <a href="https://github.com/IBM/z_ansible_collections_samples/tree/main/zos_subsystems/cics/provisioning">new sample</a> playbook with very little modification to provision a CICS region, and you only need to observe prerequisites similar to those for the z/OS core collection. Ansible is a great technology that helps us start adopting configuration as code patterns, which could include emulated z/OS environments as well.</p><h4><strong><em>Does the z/OS CICS Ansible collection integrate with other IBM and Red Hat products?</em></strong></h4><p>IBM z/OS Cloud Broker® helps you manage z/OS resources via the Red Hat OpenShift® API. This means that you can define a way of creating a CICS region, make a form for users to request a new CICS region, and then use the Red Hat OpenShift® API to automatically enact that request. Because Ansible playbooks are used both to implement that automation and to provision a CICS region, it’s very easy to translate the whole solution into an operator collection.</p><p>Similarly, if you have an Ansible playbook built to perform system provisioning, it’s easy to run that playbook in the Red Hat Ansible Automation Platform. I’ve heard of clients who want to develop an Ansible playbook so that they can respond automatically to a ticketing system. For example, when a ticket is submitted, an Ansible collection on the Ansible Automation Platform can be triggered to automatically build the requested system, without human intervention.</p><h4><strong><em>How do you see clients using Ansible CICS TS workflows in the future?</em></strong></h4><p>Actions like validating your environment — making sure it’s up and ready to accept work or looking for messages in the job log — can take a lot of manual steps. The CICS TS modules and Ansible tools are available to make automating those actions more accessible. If you’re interested in our Ansible collections, feel free to raise feature requests against us — we’re really looking to improve! However, you shouldn’t feel limited by what’s there today because you can always use Ansible to call an existing MVS (Multiple Virtual Storage) program yourself without having to wait for us to do that.</p><h4><strong><em>What excites you about the future?</em></strong></h4><p>I’m currently working on CICS TS modernization and we are kicking off some exciting initiatives. Overall, we’re looking at ways to make working with the CICS platform consistent with modern developers’ expectations in terms of tooling and workflows so that they can develop projects and deliver business value as fast as possible.</p><p>This article is part of the Ansible for IBM Z User Spotlight. Read our other installments:</p><p><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-bill-pereira-c28683569cc1"><strong>👉 Ansible for IBM Z: User Spotlight Series — Bill Pereira</strong></a><strong><br></strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-ipek-dedekoy-3d60c9156eed"><strong>👉Ansible for IBM Z: User Spotlight Series — Ipek Dedekoy</strong></a><strong><br></strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-mike-fontanetta-60c4a89bfe21"><strong>👉Ansible for IBM Z: User Spotlight Series — Mike Fontanetta</strong></a><strong><br></strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-jacob-emery-bc0f272c838e"><strong>👉Ansible for IBM Z: User Spotlight Series — Jacob Emery</strong></a></p><h4>Stay up to date with the Ansible User Spotlight Series and Ansible for IBM Z community</h4><p>Join the IBM Z &amp; LinuxOne community <a href="https://www.ibm.com/community/z/software/ansible-for-ibmz">topic group for Ansible for IBM Z</a>. If you want to join our Ansible for IBM Z Community Guild monthly calls, where the IBM Z team and Ansible customers share roadmaps on content, use cases, and collaborate on Ansible adoption, fill out <a href="https://wkf.ms/3y0ZUSV">this enrollment form.</a></p><p>Here are some additional resources if you are interested in getting started automating with Ansible for z/OS:</p><ul><li><a href="https://www.ibm.com/support/z-content-solutions/ansible/">Ansible Content Solutions</a></li><li><a href="https://docs.ansible.com/ansible/2.9/modules/modules_by_category.html">Ansible documentation</a></li><li><a href="https://ibm.github.io/z_ansible_collections_doc/index.html">Ansible collections</a></li><li><a href="https://ibm.biz/BdfakN">Ansible for IBM Z videos on IBM Media Center</a></li></ul><p><strong>The Ansible for IBM Z User Spotlight Series Team</strong></p><p><em>AJ Dyer is a Senior UX Researcher at IBM. The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd60c489a82d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-stewart-francis-dd60c489a82d">Ansible for IBM Z User Spotlight Series: Stewart Francis</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ansible for IBM Z User Spotlight Series: Jacob Emery]]></title>
            <link>https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-jacob-emery-bc0f272c838e?source=rss-a0cf28d08eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc0f272c838e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ansible-for-ibm-z]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[AJ Dyer]]></dc:creator>
            <pubDate>Tue, 23 Apr 2024 14:02:22 GMT</pubDate>
            <atom:updated>2026-03-23T21:52:46.145Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this series, we shine a light on the people who make the Ansible for IBM Z community thrive. We share the inspiring stories of users who combine experience, skill, and curiosity to shape strategies, influence organizations, and take our tools to new heights.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_lQvvY8jrbs2R7Ve6qrpOw@2x.png" /><figcaption>The Ansible for IBM Z User Spotlight Series banner</figcaption></figure><h3><strong>Getting to know Jacob Emery</strong></h3><p>Jacob Emery currently serves as the Ansible focal for the IBM Washington Systems Center. Jacob’s work includes collaborating across teams to help drive Ansible for Z adoption, leading workshops and proof-of-concept projects for clients, as well as developing custom Ansible automation to help his team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kkm33GFsX77FUNX5o90FEA@2x.png" /><figcaption>Our Featured Ansible for IBM Z user</figcaption></figure><p><strong>Tell us about your career journey so far.<br></strong>During the IBM Summit Program, I received six months of sales training and six months of Z-specific technical training. I feel so lucky to be part of a company that invests so much in its people.</p><p>In my current role, I focus on helping our clients build their Ansible for IBM Z and LinuxONE skills. I also continue to develop automation and grow my own skills in the process.</p><blockquote><strong>“Ansible is ubiquitous in the distributed world, it opens up the talent pool and enables newcomers to be helpful sooner.”</strong></blockquote><p><strong>Why the focus on Ansible?<br></strong>I really wanted to help ease the load of my IBM Z &amp; LinuxONE team. But when I joined the IBM Z space, people would say, “Don’t expect to be all that helpful for five years.” That was disheartening.</p><p>Long-time mainframe experts are stressed about leaving a huge skills gap when they retire and I think younger people expect to have shorter tenures at any given company. So although newcomers <em>want</em> to be helpful, they’re staring up at this cliff of knowledge and are unsure about how to start climbing it — or whether they want to climb it at all.</p><p>This puts pressure on companies to simplify the mainframe learning process. You can use Ansible to lower that learning curve by codifying the knowledge of long-term mainframe experts. Moreover, since Ansible is ubiquitous in the distributed world, it opens up the talent pool and enables newcomers to be helpful sooner.</p><p>In my case, choosing to focus on Ansible has helped me alleviate the pressure on my team and reduce the skills gap for those who come after me. Thanks to Ansible, I have been measurably helpful to my team in far less than 5 years!</p><p><strong>You currently work with the IBM Washington System Center. What’s it like?<br></strong>The Washington System Center (WSC) is a group of subject matter experts who have deep knowledge of IBM Z and LinuxONE. Our primary mission is to provide Z-specific expertise to our clients. We support technical sales by giving presentations and briefings, or by setting up and hosting demos and proof-of-concept work, usually for complicated or time-intensive projects. We also create videos, work on special projects, and occasionally support development efforts. We also run Wildfire Workshops. The WSC is a really cool team to be part of.</p><p><strong>How did you become the Red Hat Ansible focal for the WSC? <br></strong>I worked on a project with my mentor, Philip Wilson. He wanted to try OpenShift on IBM Z, but installing the platform was challenging, so he decided to use Ansible to automate the installation. I made it my IBM Summit Program practicum project to help him create that automation.</p><p>I fell in love with Ansible during that project. It’s just so powerful. You can touch so many areas of the stack and skill up quickly. Once I had some Ansible skills, I started getting requests to create other custom automations. After completing a few projects, people started asking me about Ansible in general.</p><p><strong>Is the WSC doing more with Ansible?<br></strong>Yes! Last year we began setting up the infrastructure to overhaul our processes through automation. Ansible Automation Platform is key because it helps us share our playbooks across the IBM Z Ecosystem team, which includes teams like the Dallas Independent Software Vendor Center. This is a big change at the WSC, and Ansible is a core part of our effort.</p><p><strong>Any specific processes that you’re looking to automate next?<br></strong>Like many mainframe teams, our z/OS and infrastructure experts are consistently swamped, so our initial use case is to set up a self-service portal for automated z/OS provisioning.</p><p><strong>You mentioned Wildfire Workshops. What are those?<br></strong><a href="https://www.ibm.com/support/pages/mainframe-system-education-wildfire-workshops-washington-systems-center-wsc">Wildfire Workshops</a> are free workshops that the WSC provides to share knowledge about IBM Z and LinuxONE with clients and partners. They’re regularly scheduled and can also be held by client request. They’re very popular.</p><p>I hosted the first Ansible for IBM Z Wildfire Workshop in November 2023. I was originally building a hands-on lab, but then a huge wave of interest hit after IBM and Red Hat announced support for Red Hat Ansible Automation Platform (AAP) on IBM Z and LinuxONE. I realized that it was time to share my Ansible knowledge through a Wildfire Workshop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cIH9pLNdY1u0ay3KK0BwgQ.jpeg" /><figcaption>Jacob Emery (top left) and Bryant Panyarachun (top right) leading a Wildfire Workshop for a client.</figcaption></figure><blockquote><strong>“Ansible is like the glue of the IT world — it can help you understand countless integration possibilities, and then act to bring diverse systems together.”</strong></blockquote><p><strong>Tell us about your Workshop attendee experience.<br></strong>We build knowledge from the ground up, so if you’re curious about how Ansible, IBM Z, and LinuxOne can work together, this workshop is for you. We’ve helped people in many roles — systems programmers, application developers, z/OS admins, and ops teams, technical managers, site reliability engineers, and even people overseeing the entire IT stack. And beginners are welcome!</p><p>We start with the basics: <em>What is Ansible? What is it used for? What’s a playbook, a module, a collection? Why is idempotency important? </em>We then apply these basics to IBM Z with hands-on exercises.</p><p>Attendees <strong><em>love</em></strong> the hands-on labs! We provide useful playbooks and some basic building blocks, such as adding a user, creating a user directory entry, generating a user password, and sending that user an email. Attendees can create a data set with a survey form through AAP, where they can select options from a dropdown and multiple choice questions.</p><p>At the end of the workshop, attendees get their own instance of Ansible Automation Platform running on IBM Z, and their own instance of z/OS to automate. Mainframe teams can use these instances to understand what’s possible before they start a full project. Along with time, automating real-world processes can take a lot of mental and emotional investment, so to experience what life can be like with a finished project is very valuable. As far as I know, this workshop is unique in delivering this kind of experience.</p><p>Overall, attendees learn that they don’t necessarily need to know how to use ISPF panels or a 3270 emulator, or how to submit JCL to create a partitioned data set. They see that they can use Ansible to integrate z/OS operations into larger cross-platform processes. And they realize that newcomers can get up and running quickly on the mainframe, which is critically important.</p><p><strong>Any highlights from your recent Workshops?<br></strong>The ‘light bulb moments’ are always a highlight. When everything starts to click for our attendees, their eyes widen as they begin to realize the possibilities. They often start ideating with their teams right in the workshop!</p><p>Another highlight is the buzz in the room that happens every time our attendees work directly with the technology in the hands-on labs. One attendee literally squealed with excitement as they opened the lab and saw the certificate renewal playbooks! They could instantly visualize a future where their lives are simpler. I love getting to show that to people.</p><p>I think everyone should learn Ansible, so it’s great when we work with attendees, especially young people, who want to learn and use Ansible to be helpful to their mainframe team. They see ways to have a big impact because Ansible is like the glue of the IT world — it can help you understand countless integration possibilities, and then act to bring diverse systems together. It’s not hard to learn, it’s getting easier, and a little Ansible knowledge goes a long way.</p><p><strong>What excites you about the future of Ansible?<br></strong>It’s exciting to think that more people in the IBM Z space will see the value of Ansible and join the community. Once a thriving community exists, network effects take over.</p><p>We see this in the distributed space. Thanks to the open-source community, no one is working on Ansible from scratch. That’s where I think and hope we’re headed. When we reach the point, the entire IBM Z community can become productive faster as more Z automations are contributed as open-source Ansible assets.</p><blockquote><strong>“If you codify the knowledge of your experts into Ansible playbooks now, newcomers can more easily continue that mission-critical work for years to come.”</strong></blockquote><p><strong>What emerging capabilities have your attention?<br></strong>The latest version of <strong>IBM watsonx Code Assistant for Ansible Lightspeed</strong> is mind-blowing! This is the new generative AI capability specifically tuned for Ansible. I’m especially excited for z/OS since there’s a strong use case for faster, easier playbook development for the mainframe.</p><p>I’m also excited about the <strong><em>z/VM collection</em></strong>. I’ve done a lot of automation with KVM, but a large percentage of mainframe clients virtualize with z/VM. This previously untouched area for Ansible will be a lot easier.</p><p>I’m also looking forward to <strong><em>Event-driven Ansible</em></strong>. It’s very powerful and I can’t wait to see what z/OS integrations emerge. I can imagine integrating MQ with Instana, and Splunk. Qradar, or ServiceNow. There are many great use cases that can happen with Event-driven Ansible that were previously impossible.</p><p><strong>In your view, why should clients adopt the Ansible ecosystem for IBM Z or LinuxONE?<br></strong>The most important message I can convey is that Ansible helps with skills for the mainframe. Adopting Ansible alleviates stress on the mainframe team today and lowers the barrier to entry for future team members. If you codify the knowledge of your experts into Ansible playbooks now, newcomers can more easily continue that mission-critical work for years to come.</p><p>If you have questions, or if you’d like to set up a workshop and are a technical salesperson from IBM or are representing a client directly, contact Jacob Emery at <a href="/service/mailto:jacob.emery@ibm.com">jacob.emery@ibm.com</a>.</p><p>For general enrollment workshops, visit the <a href="https://ibm-zcouncil.com/events-calendar/">Z Council Events Calendar</a>.</p><p>This article is part of the Ansible for IBM Z User Spotlight. Read our other installments:</p><p><strong>👉</strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-bill-pereira-c28683569cc1"><strong> Ansible for IBM Z: User Spotlight Series — Bill Pereira</strong></a><strong><br></strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-ipek-dedekoy-3d60c9156eed"><strong>👉Ansible for IBM Z: User Spotlight Series — Ipek Dedekoy</strong></a><strong><br></strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-mike-fontanetta-60c4a89bfe21"><strong>👉Ansible for IBM Z: User Spotlight Series — Mike Fontanetta</strong></a></p><h4>Stay up to date with the Ansible User Spotlight Series and Ansible for IBM Z community</h4><p>Join the IBM Z &amp; LinuxOne community <a href="https://www.ibm.com/community/z/software/ansible-for-ibmz">topic group for Ansible for IBM Z</a>. If you want to join our Ansible for IBM Z Community Guild monthly calls, where the IBM Z team and Ansible customers share roadmaps on content, use-cases, and collaborate on Ansible adoption, fill out <a href="https://survey.alchemer.com/s3/7303722/Ansible-for-IBM-Z-Community-Guild-Enrollment">this survey</a>.</p><p>Here are some additional resources if you are interested in getting started automating with Ansible for z/OS:</p><ul><li><a href="https://www.ibm.com/support/z-content-solutions/ansible/">Ansible Content Solutions</a></li><li><a href="https://docs.ansible.com/ansible/2.9/modules/modules_by_category.html">Ansible documentation</a></li><li><a href="https://ibm.github.io/z_ansible_collections_doc/index.html">Ansible collections</a></li><li><a href="https://ibm.biz/BdfakN">Ansible for IBM Z videos on IBM Media Center</a></li></ul><p><em>A big Thank you to Dan Jast, and Nate Myers for your hard work and contributions to this article.<br>Special thanks to Brian Le, for his great visual design contributions to this series.</em></p><p><em>The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc0f272c838e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-jacob-emery-bc0f272c838e">Ansible for IBM Z User Spotlight Series: Jacob Emery</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ansible for IBM Z User Spotlight Series: Mike Fontanetta]]></title>
            <link>https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-mike-fontanetta-60c4a89bfe21?source=rss-a0cf28d08eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/60c4a89bfe21</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[users]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[AJ Dyer]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 15:02:08 GMT</pubDate>
            <atom:updated>2026-03-23T21:38:33.313Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this series, we shine a light on the people who make the Ansible for IBM Z community thrive. We share the inspiring stories of users who combine experience, skill, and curiosity to shape strategies, influence organizations, and take our tools to new heights.</em></p><h3>Getting to know Mike Fontanetta</h3><p>Mike Fontanetta is well-known in the mainframe community. He’s had a rich career spanning multiple decades, experiences, roles, technologies, and organizations. Mike is recognized as a Distinguished Technologist at Ensono, where he currently works in the Product and Technology Organization leading mainframe innovation engineering.</p><h4>Q: Tell us about your career journey so far.</h4><p>I started with the mainframe before PCs were invented. I first worked the third shift in computer operations. I moved through jobs often, averaging two years at any given place. I’d work hard, rise quickly through the ranks, get one or two promotions, and then move to another organization. Back then, much like today, there were lots of opportunities in the marketplace.</p><p>During this early period, I did DASD (direct access storage device) management and was introduced to SMF (System Management Facilities) data. I also started teaching myself to program in various languages, including COBOL and Assembler. In those days, hardware and systems broke frequently, so system programmers would come in at night and on the weekends to fix them. I spent time with them and learned how the equipment worked, both programmatically and physically.</p><p>I eventually became a system programmer, but I decided to pursue a role that didn’t require me to work nights and weekends, so I took a hands-on technology role in capacity planning. Later, I led global capacity management at a company that was bought by Ensono. The new owners wanted Ensono to grow. And indeed, they doubled their revenues in the first year. Since then, they’ve grown to about 800 million USD in revenue per year. I jumped in early and started helping them sell services, but also volunteered to help during other sales opportunities; I wanted to make sure that we left the best impression on clients from a technology point of view.</p><p>While running capacity management at Ensono, I was asked to help assist their Advisory and Consulting practice. My role was to advise clients on their mainframe needs, including sizing and upgrade strategies, so I became the person who talked about new and leading-edge technologies. This led me to get involved with growing communities, like the Ansible Guild.</p><p>Soon after, I started running Engineering and got my own engineering mainframe, which is what I’ve been working toward my entire life. I started working on Python, ZOAU, and automation with Ansible. I soon needed a team member, so I hired Steven Perva, and together we held down the fort on the innovation side of Ensono. As an organization, we focused more on the non-mainframe platform with Ansible than the mainframe platform. We’ve had a lot of success, and we’re starting to get traction on the mainframe side. We also present at all the conferences, are involved in all the guilds, and make sure to stay in tune with IBM and all the major vendors, regardless of their stature in the industry.</p><blockquote><strong>“We’ve proven that we can save thousands of hours by leveraging Python and ZOAU and driving automation through Ansible.”</strong></blockquote><h4>Q: What is your perception of the mainframe and overall IT today?</h4><p>I’ve been saying for years that the mainframe is another server in the hybrid IT ecosystem, so we should promote equality and lower the barriers between platforms. Instead of dedicated mainframe system programmers or Linux system admins, we should have system administrators who can administer both mainframe and Linux systems. Linux on Z and UNIX System Services within z/OS are often not core competencies of z/OS system programmers, so we should get mainframe system programmers and Linux system admins working together.</p><p>I envision a time in the future when the silos between mainframe system programmers and Linux sysadmins will be a historical footnote. As an example, while I’m assigned to the mainframe line of business in the Product and Technology organization, my work developing automation is no longer an activity that is focused exclusively on the mainframe.</p><h4>Q: How does your approach compare to that of others in similar roles?</h4><p>I’m an outlier. What you’ve heard about system programmers being set in their ways and resistant to change is rather prevalent. For example, we often hear that they don’t want to use Python when they can use REXX. My response is that we must be ready for the future. We must make sure that the next generation of system programmers is prepared. They’re learning Ansible and Python in school, not REXX. We need to pivot to these new languages.</p><h4>Q: You’ve been named an <a href="https://developer.ibm.com/champions/">IBM Champion</a> for 2023. What does that mean to you?</h4><p>It’s unbelievably flattering. I’ve invested a lot of my time professionally to get to where I’m at today. This recognition, as well as having received the Challenge Coin Award — one of only two coins to be awarded outside of IBM — has been a humbling experience.</p><h4>Q: What exciting things are you working on lately?</h4><p>I’m actively working on several significant projects, and I’ll share a high-level on a couple that you might find interesting.</p><p>Envision is an Ensono-developed IP that provides a single pane of glass view for all platforms we support for clients. We’ve recently introduced Envision Advisor to this stack, which provides actionable insights for clients on supported systems. My team has active projects to introduce the mainframe-focused insights to Envision Advisor.</p><p>My group, Innovation Engineering, is developing a mainframe auto-discovery solution that keeps our CMDB (Configuration management database) accurate and up-to-date for the large number of assets that we manage. We’re leveraging my team’s IP in conjunction with a vendor’s automated discovery offering to cover the areas where the vendor’s product has gaps. I’m also providing recommendations to the vendor on how to improve their product as well.</p><h4>Q: How did you get started with Ansible?</h4><p>Ansible wasn’t something I went looking for on my own. At the time, Python had just been introduced on the mainframe and ZOAU had just been released. I saw Python as an opportunity to bring back a level of programming for us as technologists, so we were really focused on those solutions. An IBM team introduced me to Ansible. After I saw how Ansible can help make things happen quickly, automate things effectively, simplify complicated problems, and make things work better overall, I started to view Ansible as our most viable solution.</p><h4>Q: You discovered that Ensono was already using Ansible, but not in the mainframe space. How did you leverage your company’s prior experience with Ansible?</h4><p>Discovering that Ensono used Ansible on other platforms quickly had me engaged with our internal team, and I’ve remained connected and tracked with their projects ever since. Our team is doing interesting things with Ansible and it has continued to be of high interest to me.</p><p>Ansible and Python being platform-agnostic made connecting with other Ansible users and teams easier. By sharing experiences of how Ansible could be leveraged, we found commonalities between the outcomes we’re each driving forward. We’re currently leveraging my innovation mainframe as the Ensono Ansible mainframe lab environment, which provides a common environment for us to gain experiences.</p><blockquote><strong>“The capability to scale and run things in parallel is something that we never would have achieved without something like Ansible.”</strong></blockquote><h4>Q: Ansible can unite the distributed, networking, and mainframe areas of the business. Did that interest you?</h4><p>Having the capability to initiate and update common processes across our supported environment was high on the list of desired outcomes. While my focus was the mainframe platform, other teams have a similar interest in the distributed and networking environments. One of the unexpected outcomes was our alignment and partnering with the other platform teams.</p><p>Like most organizations over time, we’ve deployed scripted processes to LPARs to complete common activities. These processes are a key component of our support capability, and in many cases are similar across clients. What Ansible provides is the ability to maintain and deploy updates at a greater velocity. We’ve also found that more complexity can be developed using Python and ZOAU scripting. This really takes us to the next level of capabilities.</p><p>Using Ansible, we developed complex scripts that give us an automated way to engage with multiple LPARs and analyze dozens of subsystems at the same time. The capability to scale and run things in parallel is something that we never would have achieved without an Ansible solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*jLzYnrgwCSsYtg0A2hYOww.png" /></figure><h4>Q: Ensono is a managed service provider. How do your clients react when they hear that you’re using Ansible to manage their environments?</h4><p>Our experience has been that clients are accepting the changes needed to enable Ansible. I was directly involved with reaching out to clients to obtain approval for these changes, and during those conversations, virtually every client said, “We need this for ourselves, and we need to do this to our own application checks. This will help us reduce the time it takes to test and validate applications.”</p><h4>Q: How do you help others warm to your perspective on Ansible?</h4><p>I present my case through facts and measured success. For instance, by using a Python Ansible script, we can set up a new CICS region in about 15 minutes. It takes teams significantly longer (hours) to complete this same task. When I meet with teams, I demonstrate how we improve coverage and save thousands of hours, and how they can, too. But I always give them an opportunity to describe how they’re going to check thousands of CICS regions — at 20 minutes per region — in a two-hour timeframe. If they can show me how that’s possible, then I’m interested in hearing more. But if they can’t, then I ask if I can show them how to do it with Ansible.</p><h4>Q: What other pain points have Ansible or ZOAU solved for your organization?</h4><p>The short answer is that we found Ansible and Python are future-proofing support capabilities for our client’s critical environments. Ansible scripts using Python and ZOAU have aided in addressing the new hire skill gap. We can now leverage Python, the most popular language in the industry today. Many of our new hires have Python experience, and this expedites the learning curve.</p><p>Team members who have been in IT for a longer time like me have developed REXX skills and scripts over the years. We’ve been able to demonstrate how those scripts can be executed through an Ansible playbook. The REXX scripts can be used as-is. In some cases, those scripts are being re-imagined through Python with more advanced capabilities.</p><p>Our clients benefit because we can leverage existing legacy scripting as needed, and then when new associates re-develop scripts, they gain experience with REXX syntax. This has been shown to be beneficial to everyone.</p><h4>Q: How can IBM help Ansible and ZOAU grow?</h4><p>Many organizations are moving to a managed service-provider relationship, and clients recognize the benefits. That said, many Ansible collections aren’t geared toward managed service providers. We do our best to leverage the collections — they’re well-written and usable — but we often find that the collections are better suited for a standalone organization than for the scale of environments that we support.</p><p>Another challenge is communicating playbook execution success to z/OS system programmers. Today they must log into the console to track results. To address this, we completed an MVP workflow that communicates with our ServiceNow environment. We see this as a possible path forward as we update tickets automatically and communicate results with the system programmers and operational teams.</p><h4>Q: What’s your view of open-source software on the mainframe?</h4><p>Open-source solutions (OSS) have been available for years on the CBT tape, for example. While not necessarily new, the types of OSS available today are very different and more common than those used on Linux systems. I feel OSS is a component of the modern cloud-connected mainframe, and its adoption is critical to long-term platform success. The biggest challenge is security, which is something we must be vigilant about and focused on. I believe it’s up to developers to ensure that their solutions are secure, and for us to test and validate that those solutions are secure, to verify that the developers are following best practices.</p><h4>Q: Are there other success drivers for the mainframe?</h4><p>Lowering the barriers between different platforms is critical. Whether managing mainframe, Linux, or Windows server farms, what we really need is the capability to administer an overall IT ecosystem through unified teams. We should have a standard approach regardless of platform, processing, or data storage location. I know some people feel that this is a utopia we likely won’t see in the near future, and I don’t disagree, but to me, it’s the direction we need to move toward.</p><h4>Q: You’ve had an amazing run with the mainframe. Any advice on how experienced mainframers can help persons new to the platform?</h4><p>Back in the day, you learned quickly through experiences, because hardware and software failed more frequently. Restoration of service was critical which had us lean in and correct the issue as soon as possible. With that in mind, my advice to experienced mainframers is to help the newer people be exposed to that kind of learning. To encourage them to jump on the mainframe and dedicate time to it, invest the time in learning and obtaining as much hands-on experience as possible.</p><p>This article is part of the Ansible for IBM Z User Spotlight. Read our other installments:</p><p><strong>👉</strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-bill-pereira-c28683569cc1"><strong> Ansible for IBM Z: User Spotlight Series — Bill Pereira</strong></a><strong><br></strong><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-ipek-dedekoy-3d60c9156eed"><strong>👉Ansible for IBM Z: User Spotlight Series — Ipek Dedekoy</strong></a></p><h4>Stay up to date with the Ansible User Spotlight Series and Ansible for IBM Z community</h4><p>Join the IBM Z &amp; LinuxOne community <a href="https://www.ibm.com/community/z/software/ansible-for-ibmz">topic group for Ansible for IBM Z</a>. If you want to join our Ansible for IBM Z Community Guild monthly calls, where the IBM Z team and Ansible customers share roadmaps on content, use-cases, and collaborate on Ansible adoption, fill out <a href="https://survey.alchemer.com/s3/7303722/Ansible-for-IBM-Z-Community-Guild-Enrollment">this survey</a>.</p><p>Here are some additional resources if you are interested in getting started automating with Ansible for z/OS:</p><ul><li><a href="https://www.ibm.com/support/z-content-solutions/ansible/">Ansible Content Solutions</a></li><li><a href="https://docs.ansible.com/ansible/2.9/modules/modules_by_category.html">Ansible documentation</a></li><li><a href="https://ibm.github.io/z_ansible_collections_doc/index.html">Ansible collections</a></li><li><a href="https://ibm.biz/BdfakN">Ansible for IBM Z videos on IBM Media Center</a></li><li><a href="https://survey.alchemer.com/s3/6603851/Ansible-for-IBM-Z-Survey-NPS-Survey">Ansible NPS survey</a></li></ul><p><em>Special thank you to @dan.jast1, Nate Myers, and Kathryn Briscoe for your hard work and contributions to this article.</em></p><p><em>Andreina Dyer is a UX Research Lead at IBM. The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60c4a89bfe21" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-mike-fontanetta-60c4a89bfe21">Ansible for IBM Z User Spotlight Series: Mike Fontanetta</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Patterns Next Level Design Program: Elevating Design Leadership and Expertise]]></title>
            <link>https://medium.com/design-ibm/patterns-next-level-design-program-elevating-design-leadership-and-expertise-a2818ac4254e?source=rss-a0cf28d08eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2818ac4254e</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[patterns]]></category>
            <dc:creator><![CDATA[AJ Dyer]]></dc:creator>
            <pubDate>Tue, 26 Sep 2023 18:08:55 GMT</pubDate>
            <atom:updated>2026-03-23T21:40:00.302Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Authors:</em></strong><em> Andreina Dyer and Maryann Slama</em></p><p>The <em>Patterns Next Level design program</em> is a cohort-based program for band 8 &amp; 9 designers that takes place over 14 weeks. This newly launched program is meant to strengthen a designer’s technical and managerial leadership skills, elevate their career eminence, and expand their internal professional networks. The program comprised key areas of development including business impact, inclusive leadership, storytelling, inclusive critique and feedback, craft expertise, and equitable AI and ethics. The wealth and caliber of resources and weekly speakers were outstanding and fomented a deeper sense of belonging and inspiration to its participants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AYQjzHOtTVqjec_IulItfg.png" /><figcaption>The Patterns Next Level Program Universe</figcaption></figure><h4>Program’s Structure</h4><p><strong>Live Sessions<br></strong>The weekly live sessions provided us with an open platform for our design leaders to share their personal and professional experiences and how they have personally applied that week’s specific theme to advance their careers. These sessions were eye-opening and offered all program participants a unique opportunity to gain insights and better comprehend how design decisions influence a company’s bottom line. Above all, these sessions inspired us to approach our work more strategically, no matter what area of design we were in.</p><p><strong>Asynchronous Learning Sessions<br></strong>To supplement the live talks and group discussions, curated and upskilling resources were provided that enabled us to dive deeper into any weekly theme. These ranged from video clips to articles, to ebooks, and more. It helped address the fact that each of us had slightly different skills we wanted to strengthen. These resources helped us tailor our Patterns experience to focus on exactly the topics most relevant to us.</p><p><strong>Lightning Talks<br></strong>The program included two lightning talk sessions that prompted us to delve into topics outside our comfort zones and share that new knowledge with the wider IBM Design community. This approach was an original way to foster an environment of intellectual exploration and risk-taking by way of encouraging different formats and presentation styles. We were able to learn to embrace the challenge of researching and presenting on unfamiliar topics, hence cultivating adaptability and domain knowledge. Moreover, encouraging critique and feedback from fellow program participants right after each presentation provided everyone with a fresh perspective that embraced creativity and resilience. In essence, these lightning talk sessions became a crucible for personal growth and innovation, where we not only shared our expertise but also learned the art of embracing the unknown, a skill that serves us well throughout our professional journeys.</p><p><strong>Coaching Sessions<br></strong>The Patterns Next Level program leaders emphasized the impact of coaching on growth; and coaching from both design leaders and from peers. We were encouraged to meet with coaches who focused not on providing advice, but who guided reflection through thoughtful questioning. We were lucky enough to find coaches with experience in UX research and coaching certification. It was incredibly effective in helping us clear through mental fog and see our goals with much more confidence.</p><p>Overall, the entire program acted as a thoughtfully curated menu of career-growth activities. There were easily consumable and engaging sessions as well as asynchronous materials to dive deep into if you wanted to prioritize any specific topic. Although there wasn’t enough time to fully participate in every option on the menu, it was a useful activity in prioritization; a way of nudging you towards focusing on specific areas of growth. If you wanted to grow in storytelling and public speaking, there was ample opportunity in the lightning talk activities. If you wanted to expand your network, they matched you with a weekly partner to meet and share experiences with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N55tf3H5ynF62ecnBVA-Og.png" /><figcaption>Patterns Next Level Program Weekly Themes and Activities</figcaption></figure><h4>Key Takeaways</h4><p><strong>1. Design Knowledge <em>is</em> Domain Knowledge<br></strong>Domain knowledge for designers really means knowing enough to understand why you are doing something and what the impact of that means to our users. Having domain knowledge does not require you to <em>completely</em> understand the ins and outs of your product or even be able to use it yourself; it means understanding how to apply and leverage your knowledge and expertise of design into your product and the surrounding elements that interact with it.</p><p><strong>2. Eminence doesn’t happen overnight. It’s a continual journey <br></strong>Your eminence <em>aka</em> personal brand is what you are known for. Whether it is leading and delivering data-driven deliverables across products or being a community-organizing wiz, you build eminence through sustained and consistent effort, not that one independent project or event.</p><p><strong>3. Connections are a bridge for inspiration<br></strong>Connections are more than just networking, they are also meant to give you opportunities for alignment and inspiration. When we open up ourselves to connect beyond our immediate circle, we open up to new ideas, perspectives, and uncommon opportunities. Meaningful connections that challenge our status quo have the potential to ignite our creativity and take us in a whole different direction with our projects and even our careers. Connection, at its core, is a catalyst for the inspiration that can transform both our personal and professional lives.</p><p><strong>4. Take time to know yourself <br></strong>When we hear career planning, we often think of moving on to the next band level or promotion, but it can mean so much more if you really understand what it is that you need and want your career to become. Career planning can also mean aligning your role with efforts that really speak to you and that are closer to what you envision your day-to-day to be. It can also mean learning another set of skills that the team needs and aligns with doing more of that thing you want to be known for at your organization. The hardest part of career planning is knowing what you are planning for, but ultimately it should be aligned with your happiness and developing the best version of yourself in mind.</p><p><strong>5. Business Impact is Design Impact<br></strong>Aligning design work with OKRs and KPIs is crucial for demonstrating the impact of your efforts, and ensuring that your design activities are aligned with business priorities. However, it’s important to note that while aligning design work with business priorities is essential, not all business priorities should be exclusively dependent on design activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JjuzKKnUpC4AZgUFCiQRA.png" /><figcaption>Design activities tied to business priorities have a deeper impact on an organization</figcaption></figure><p><strong>6. Block time in your week for professional development<br></strong>The structure of Patterns Next Level was fantastic for keeping us focused and on track to intentionally invest in our careers. Whether you’re in the program or not, block regular time in your schedule to reflect and invest in yourself.</p><p><strong>7. Get out of your bubble<br></strong>Some of the most interesting and insightful conversations we had during the program were with colleagues who were in a similar career stage (and reflecting on similar questions) but had different experiences due to being in a different area of the company. It was really helpful in finding out which questions and challenges are ‘normal’ and which are more unique to us.</p><p><strong>8. Identify gaps in your map<br></strong>We’ve found that confidence in our plans come in large part from being confident that we are not <em>missing something</em>. Having trust in our decision-making skills is important, but if we don’t trust the data source that we have to support those decisions, how do we move forward? how can we really trust those decisions? The first step is to reflect and make clear where our knowledge gaps are. Only then can we work to fill those gaps.</p><p><strong>9. Form an MVP understanding of your career options (at a minimum)<br></strong>Once you’ve identified your knowledge gaps, work to get a minimal, but functional, model of your career options. You can build it out later, but there are huge gains to be had by simply forming a basic model that you can work from.</p><p><strong>10. Build a cohort of colleagues<br></strong>Throughout our careers at IBM, it’s been invaluable to have a group of colleagues we can reach out to, bounce ideas off of and ask advice from. We often hear about how important it is to have mentors who are a step ahead of you, but it’s also important to have peer mentors who know what it’s like to face the challenges you’re facing because they’re in the weeds there with you.</p><h4>Acknowledgments</h4><p>Thank you to Stacey Seronick, Nicole Umphress, and the entire Patterns team for your work in making IBM Design a great place to grow. Thank you to our managers, Mario Perotti &amp; Kristine Berry, for your continued support and investment in our careers. Cheers!</p><p><em>The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2818ac4254e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/patterns-next-level-design-program-elevating-design-leadership-and-expertise-a2818ac4254e">Patterns Next Level Design Program: Elevating Design Leadership and Expertise</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ansible for IBM Z: User Spotlight Series —  Ipek Dedekoy]]></title>
            <link>https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-ipek-dedekoy-3d60c9156eed?source=rss-a0cf28d08eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d60c9156eed</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ibm-z]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ansible]]></category>
            <dc:creator><![CDATA[AJ Dyer]]></dc:creator>
            <pubDate>Mon, 26 Jun 2023 14:31:37 GMT</pubDate>
            <atom:updated>2026-03-23T21:40:35.304Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ansible for IBM Z: User Spotlight Series — Ipek Dedekoy</h3><p><em>In this series, we shine a light on the people who make the Ansible for IBM Z community thrive. We share the inspiring stories of users who combine experience, skill, and curiosity to shape strategies, influence organizations, and take our tools to new heights.</em></p><h4><strong>Get to know Ipek Dedekoy</strong></h4><p>Ipek currently works as a z/OS middleware system programmer at Rabobank and is a member of their newly formed Ansible-focused Automation Squad. After completing her bachelor’s degree in computer engineering, Ipek started her mainframe career journey as a CICS/MQ system programmer. She has experienced various mainframe systems through working at several financial institutions across Türkiye, Poland, and the Netherlands.</p><p>As a young mainframer interested in modernization, Ipek is enthusiastic about adopting and implementing new technologies into traditional processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uSOVketdwFsaUU23QYG6XQ.jpeg" /><figcaption>Ipek Dedekoy next to the Z Mainframe</figcaption></figure><h4><strong>Q: What makes Ansible a great user experience?</strong></h4><p>First and foremost, the documentation is very well put together and easy to read. Second, Ansible is very easy to learn. Third, I would say the community; although it is not very big, it is very accessible.</p><blockquote><strong>“Sharing the importance of automation is an obligation. Running tasks manually is too risky — one single mistake can be disastrous.”</strong></blockquote><h4>Q: What benefits do you see in having a full platform focused on automation?</h4><p>I like that you can see tasks running. For example, you can initiate a playbook while another playbook is already running, and you can see the real-time results of both. Also, you can quickly see the logs in a single platform without having to navigate anywhere else. I think this encompasses the definition of the hybrid cloud and how it works seamlessly. It is a very modern concept where you can — with one click — accomplish so much. It feels like I’m doing DevOps, cloud, and automation all in one place because I’m using the right tools.</p><h4>Q: What do you think it would take for everyone in your team to get behind the idea of using Ansible?</h4><p>I think it takes encouragement. Pushing them to try it is the only way that they’ll know what it’s like. It’s not enough to tell people about the benefits of Ansible. If they never use it themselves, they will never know.</p><h4>Q: How has Ansible given you a competitive advantage?</h4><p>Ansible has given me the ability to collaborate on automation technology with other teams in different parts of the business. With just five years of experience in this field, I’ve been able to get opportunities that not everyone comes across, thanks mainly to the technology of the product. Anyone can learn Ansible — anyone can do what I do. People who come to me for help getting started take that knowledge and progress on their own. When you learn something well, it’s important to talk about it and share that knowledge with others. Sharing the importance of automation is an obligation. Running tasks manually is too risky; one single mistake can be disastrous.</p><h4>Q: How has your leadership team realized the value of the work you are doing with Ansible?</h4><p>We currently hold Ansible demos and presentations for stakeholders, including system programmers, clients, application teams, and developers. They often recognize the word ‘Ansible’, but they usually don’t know how they can use it within our company. As we present, you can see them realize that we’re not talking about system automation, and they start to become aware of this different layer that they can access.</p><blockquote><strong>“Anyone can learn this — anyone can do what I do.”</strong></blockquote><h4>Q: What are the plans for 2023?</h4><p>We will continue working on Certificate automation, but there is also a lot of interest in automating everyday tasks from individuals and teams not directly related to the mainframe. I have been working with some of them to get them started as soon as possible. That way, they can use their Ansible knowledge to automate other tasks. A lot of ideas and brainstorming sessions are taking place for what’s coming in 2023, and I’m looking forward to seeing what’s next.</p><h4>Q: How do you envision the future of the mainframe?</h4><p>I think it will continue to develop further. Even now we can see the progress, but it is up to the people who develop it to use automation in real mainframe areas. If people stop using and advancing mainframe automation, it will not evolve. With the new generation coming, it is more likely that change will continue, and automation will be able to accomplish great things.</p><h4>Q: What would you say to someone who is in university now and is thinking about a career in the mainframe space?</h4><p>I would tell them that they should always be open to new things. Don’t just learn from people on the job. You need to think about how to make improvements and make those changes. If you are interested in doing the same thing every day, then the mainframe is not for you. This space allows you to do new things and apply innovative ideas if you have the initiative to do so. Automation might sound a little scary for some who think that it will take their jobs, but in reality, it is a great space for opportunity in the mainframe.</p><p>This article is part of the Ansible for IBM Z User Spotlight. Read our other installments:</p><h4>👉<a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-bill-pereira-c28683569cc1"> <strong>Ansible for IBM Z: User Spotlight Series — B</strong>ill Pereira</a></h4><h4>Stay up to date with the Ansible User Spotlight Series and Ansible for the IBM Z community</h4><p>Join the IBM Z &amp; LinuxOne community <a href="https://www.ibm.com/community/z/software/ansible-for-ibmz">topic group for Ansible for IBM Z</a>. Below are some additional resources if you are interested in learning more about automating with Ansible for z/OS:</p><ul><li><a href="https://www.ibm.com/support/z-content-solutions/ansible/">Ansible Content Solutions</a></li><li><a href="https://docs.ansible.com/ansible/2.9/modules/modules_by_category.html">Ansible documentation</a></li><li><a href="https://ibm.github.io/z_ansible_collections_doc/index.html">Ansible collections</a></li><li><a href="https://ibm.biz/BdfakN">Ansible for IBM Z videos on IBM Media Center</a></li><li><a href="https://survey.alchemer.com/s3/6603851/Ansible-for-IBM-Z-Survey-NPS-Survey">Ansible NPS survey</a></li></ul><p><em>Special thank you to @dan.jast1, Nate Myers, and Kathryn Briscoe for your hard work and contributions to this article.</em></p><p><em>Andreina Dyer is a UX Research Lead at IBM. The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d60c9156eed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-ipek-dedekoy-3d60c9156eed">Ansible for IBM Z: User Spotlight Series —  Ipek Dedekoy</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leading and coaching: Lessons learned from the first Patterns Amplified cohort]]></title>
            <link>https://medium.com/design-ibm/leading-and-coaching-lessons-learned-from-the-first-patterns-amplified-cohort-2778e43d7bf9?source=rss-a0cf28d08eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/2778e43d7bf9</guid>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[AJ Dyer]]></dc:creator>
            <pubDate>Wed, 29 Mar 2023 18:25:39 GMT</pubDate>
            <atom:updated>2026-03-23T21:42:57.399Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article was co-written by AJ Dyer and Orizema Cruz Pina. Both were participants of the first </em><a href="https://w3.ibm.com/w3publisher/patterns/about-patterns/patterns-amplified"><em>Patterns Amplified program </em></a><em>cohort and served as coaches for an Incubator project team in the Patterns Getting Started program.</em></p><figure><img alt="This image shows the four elements that comprised the Patterns Amplified Program: Slack communication/collaboration, asynchronous YourLearning path, synchronous learning sessions and live coaching sessions with the Incubator teams" src="https://cdn-images-1.medium.com/max/1024/1*NH9gVPlbMTKA6odt2fA_zQ.png" /><figcaption>The Patterns Amplified Universe</figcaption></figure><h3>Introducing Patterns Amplified</h3><p>Like other Patterns programs, Patterns Amplified is a cohort-focused, regionally-based virtual practicum course that takes place over 4 weeks. The program was created as a means for professional designers to strengthen their Enterprise Design Thinking (EDT) facilitation and coaching skills. Although it is recommended to Patterns Getting Started graduates, those without the experience can still participate so long as all who are interested apply via manager nomination.</p><p>Patterns Amplified was structured in a way that allowed the five participants of its first cohort to fulfill most of the requirements on their own time and at their own pace. Asynchronously, we made our way through the rigorous YourLearning path (five required sections with six to thirteen activities each, one optional section with 27 activities) while each coaching a Patterns Getting Started Incubator team. Twice weekly, the cohort met with Tom Dayton, the Amplified Program Facilitator, via Webex for education sessions on facilitation, and to practice or inquire about how to improve as coaches. We’re going to provide more information about the format and structure below.</p><h4>Synchronous Education Sessions</h4><p>The live sessions with Tom Dayton were a great time for all of us to learn and work together. It is in this safe, judgment-free environment that we were able to ask questions and experiment using sandbox scenarios. However, two hour-long live sessions a week did not mix well with our Incubator team’s timeline, making it extremely difficult to weave our learnings into their design thinking activities.</p><p>Fortunately, Tom also encouraged us to practice <a href="https://pages.github.ibm.com/Tom-Dayton/Design-Guide-Suggestions-by-Tom/3%20High%20Level%20Structure%20and%20Nav.html#Mapping-Identity-Attributes-&amp;-Actions">outlining requirements and hammering out the information architecture</a> for our home teams which gave us a better understanding of the products to which we’d be returning. If anything is to be added to this portion of Patterns Amplified, we’d hope for improved coordination with the Patterns Getting Started Incubator project, as well as alignment with the learning path.</p><figure><img alt="This image shows a closer look at one of the activitites completed during the program. It involved mapping out the business requirements, customer requirements, user requirements and technical requirements." src="https://cdn-images-1.medium.com/max/1024/1*5Sk1NxvoTlEtTnOyCCQIFQ.png" /><figcaption>The synchronous learning sessions took us on a deep dive into user requirement discovery activities that involved task objects, information architecture, and users’ mental models</figcaption></figure><blockquote><strong>“You may find that all sorts of important answers haven’t been documented because no one has dared to ask the obvious questions”</strong></blockquote><h4>Becoming a Coach</h4><p>IBM Design continues to mature with every passing year and the Patterns program plays a vital role by educating, elevating, and bringing together designers across all organizations. During Patterns Getting Started, experienced designers are often given the opportunity to connect with newly-hired Patternites by volunteering to be panelists for AMAs, presenting on personal experience with their specialty, and coaching them on <a href="https://www.ibm.com/design/thinking/">Enterprise Design Thinking</a>.</p><p>For Patterns Amplified, we were assigned to be the coaches of a Patterns Getting Started Incubator team. These teams were comprised of 5–6 designers of varying specialties (UX, visual, content, and research). As coaches, we observed the Patternites as they worked together to iterate and present weekly playbacks of their work, culminating in a final presentation of the outcomes and deliverables that the project sponsoring teams could carry forward post-program.</p><p>We were there to provide hands-on coaching to these folks as they navigated learning a new domain and providing a solution to a real IBM business problem in a matter of four weeks. Our role was focused on ensuring the team collaborated well and felt empowered to make decisions to fulfill real, complicated product needs. We were not there to fulfill the responsibilities of a director, manager, or lead so as we moved through the program, we shared personal stories and learned lessons as a way to empathize and provide practical applications of how we leverage design thinking on our home teams. Sadly, due to the intense timeframe of both Patterns programs, we were only able to impart wisdom on rare and rushed occasions.</p><h4>The Amplified Learning Path</h4><p>A program learning path was provided to us as a way to continue learning on our own time outside the synchronous sessions. There is no doubt that we learned valuable lessons throughout the self-driven entire learning path. We expanded our knowledge — on subjects ranging from the conjuncture of design and sales, facilitation methods, and the value of design, to career-planning, emotional intelligence, and management techniques — in a way that provided us with meaningful guidance we are sure to revisit throughout our careers.</p><p>Although we enjoyed the wide variety of subjects on the learning path, we had qualms with the lack of focus and continuity. Each week, our studies jumped from one subject to another, making it difficult for us to develop skills in an in-depth, orderly fashion. If each section of the learning path had been given a theme (leadership and requirements, coaching and hills, etc.) and group activities for discussing or practicing the activities that we experienced in isolation, we have no doubt that the clarity of our takeaways would have been further amplified.</p><h3>Top 10 Takeaways</h3><p><strong>1. Paths aren’t always paved well<br></strong>A learning path is an entire journey that starts from the minute it is assigned to the moment you start applying what you’ve picked up. Whether the learning path is <a href="https://elearningindustry.com/learning-path-strategies-effective-training-programs">successive, alternative, or by level, </a>you should be clear about the knowledge you are aiming to impart from the very beginning. If the goal is not clear to you, ask, because activities added and ordered intentionally will better guarantee the retention of the material.</p><p><strong>2. Work alone, together<br></strong>A great approach to coaching and facilitating is allowing the participants to think. Providing them with a space to work isolated from each other is vital to them being able to put down their ideas without feeling influenced or overshadowed by more vocal participants. Silence speaks volumes, so you want to provide that space before coming together as a group. Allowing people to<a href="https://www.mindtools.com/ak3qj17/brainwriting"> brainwrite</a> before they brainstorm generates more insightful inquiries and leads to improved conceptual ideation.</p><p><strong>3. Give questions, not suggestions<br></strong>Replacing that long list of suggestions with questions helps those you are guiding assess their understanding of the task at hand. You are not expected to have an immediate answer for everything so take time to filter your feedback; formulate insightful and supportive prompts that will trigger retrospection and further the conversation.</p><p><strong>4. Emotional intelligence is a superpower<br></strong>While technical skills and domain knowledge are important to have, emotional intelligence (EQ) is a superpower that can bring a coach’s effectiveness to the next level. EQ allowed us to navigate the complexities of our Incubator team’s interactions and mitigate risks by putting in place a social contract that outlined and expressed empathy, boundaries, and rules of engagement. When acting as a leader, being able to recognize when people are not in a good place psychologically is vital for their own success and that of the team.</p><p><strong>5. Whitewater over waterfall any day<br></strong>In order to prevent “prematurely specific solutions without good rationale”, ensure that the requirements on which you base designs are traceable up and down the hierarchy. This can be done by creating requirements using the whitewater method instead of the waterfall method, meaning participation and prioritization when creating the hierarchy is very frequent.</p><p><strong>6. Hills are linchpins!<br></strong>Hills are a type of user requirement that contain a who, what, and why (or wow!). Once your hierarchy has been fleshed out, use the “lowest strategic user requirements” as Hills for your roadmap. You may need to research and create lower, more tactical user requirements to support those Hills before moving on to technical requirements. Remember, not all user requirements will be hills, but all Hills should be user requirements that connect both throughout the hierarchy and across each role’s contributions on a team.</p><p><strong>7. Saying “No” saves lives<br></strong>If you are a design leader, be sure you are screening the requests you receive for your team’s labor. Those putting in a request should attempt to list some task objects prior to your commitment and your team’s subsequent deep dive using EDT activities. Assessing the goals, issues, and assumptions for potential projects, and making this process known, helps maintain the quality of your team’s labor as well as high morale among individual contributors.</p><p><strong>8. Double-check your seating chart <br></strong>Walking through EDT activities (such as mapping task flows and task objects) is undoubtedly an important step in the design process. However, a mistake often made is keeping this process exclusive to User Experience Designers with occasional input from Product Managers and Developers. Ask yourself: Does visual design have a seat at my information architecture table? Visual Designers must understand all concepts in order to translate the information architecture to an interface that your users can easily understand and are delighted to experience. A different perspective is also good for catching and filling gaps you might have missed, so don’t forget to involve all roles when establishing your product’s underlying mental models.</p><p><strong>9. The emperor has no clothes<br></strong>Asking “Why?” is not just for kids and the Backstreet Boys. We must all question critically and have patience for apparent ignorance among our teams. When we hear what we perceive to be obvious questions with obvious answers, don’t presume; instead, seek to understand the asker’s perspective by requesting context and investigating your assumptions. Doing so is invaluable to the development of thought fluency and critical thinking. So don’t be afraid to ask. You may find that all sorts of important answers haven’t been documented because no one dared to ask the obvious questions.</p><p><strong>10. Strive to apply in real-time<br></strong>When learning new concepts, processes, or methods, try applying them immediately to your projects or aspects of your everyday life. This aids in discovering nuances and misinterpretations, and questions you may have right off the bat.</p><figure><img alt="This image shows the pre-program and post-program self-reported confidence scores in the dimensions of the authors’ role at IBM, success at IBM, designing for enterprise, utilizing design tools, designing for accessibility and networking at IBM." src="https://cdn-images-1.medium.com/max/1024/1*h1S7tCS79I_YeMRCC5tp7Q.png" /><figcaption>The authors’ pre-program and post-program self-reported confidence scores</figcaption></figure><h3>Our Paths Forward</h3><p>In the end, Patterns Amplified opened our eyes to the resources and professionals to which we have access for continued growth at IBM. Our peek behind the curtain revealed so many talented and experienced designers and design educators. We are appreciative and thankful for their guidance and hope to return the favor by amplifying our experience, for without them there would have been no Patterns to attend.</p><p>Additionally, we had a great experience getting to know the other three participants of this cohort, who specialized in different disciplines of design. Together, we were able to better understand the concepts and benefits of the activities we did during our synchronous education sessions.</p><h4>Orizema</h4><p>I’m elated to share that Patterns Amplified gave me the knowledge to lead my home team through Tom Dayton’s Task Objects activity, and subsequently, the confidence to seek out a more challenging opportunity that better aligns with my interests. For the first time in years, I am transitioning to a new team and I can’t wait to tackle their diverse visual design needs with my amplified perspective! Hopefully, this new opportunity will one day result in promotion and thus qualification for the newest Patterns program, <em>Patterns Next Level.</em></p><h4>AJ</h4><p>Completing the Amplified program was an excellent experience and a stepping stone for further developing my leadership and coaching skills. I also feel I have built a stronger professional network that offered valuable insights, advice, and opportunities to collaborate across business units. This program has inspired me to seek out the next step in this journey which is to complete the <em>Patterns Next Level program</em> which will undoubtedly be another milestone in my career at IBM.</p><p><em>Special thank you to Tom Dayton, Stacey Seronick, and Nicole Umphress for your hard work and contributions to this article.</em></p><p><em>The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2778e43d7bf9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/leading-and-coaching-lessons-learned-from-the-first-patterns-amplified-cohort-2778e43d7bf9">Leading and coaching: Lessons learned from the first Patterns Amplified cohort</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ansible for IBM Z: User Spotlight Series — Bill Pereira]]></title>
            <link>https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-bill-pereira-c28683569cc1?source=rss-a0cf28d08eef------2</link>
            <guid isPermaLink="false">https://medium.com/p/c28683569cc1</guid>
            <category><![CDATA[ibm-champion]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ibm-z]]></category>
            <dc:creator><![CDATA[AJ Dyer]]></dc:creator>
            <pubDate>Thu, 12 Jan 2023 15:31:45 GMT</pubDate>
            <atom:updated>2026-03-23T21:43:55.233Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ansible for IBM Z: User Spotlight Series — Bill Pereira</h3><p>In this series, we shine a light on the people who make the Ansible community thrive. We share the inspiring stories of users who combine experience, skill, and curiosity to shape strategies, influence organizations, and take our tools to new heights.</p><h4><strong>Get to know Bill Pereira</strong></h4><p>Bill Pereira is a <a href="https://www.ibm.com/products/zos">z/OS </a>System Programmer and an active member of the Ansible for IBM Z community. After studying Computer Systems Analysis and Business Administration, he obtained several certifications in mainframe technology. Bill has since worked with <a href="https://www.ibm.com/topics/mainframe">mainframes</a> in several countries and is passionate about bringing modernization and new technologies to the z/OS platform.</p><p>In this quarter’s interview, we sat down with Bill Pereira to chat about his trajectory, pivotal moments, and his take on modernization tooling.</p><h4>Q: Bill, tell us a bit about your career journey so far.</h4><p>I started working as a Console Operator at IBM about 12 years ago. Then I started doing deeper work as a Systems Programmer in Brazil and Poland. I was interested in working with other technologies and played around a bit as a developer. I also began participating in technology events, such as <a href="https://www.share.org/">SHARE</a> and <a href="https://www.gse-nordic.org/">GSE</a>. I became fascinated with Node.js and cloud computing, so I started exploring <a href="https://www.ibm.com/docs/en/zos/2.2.0?topic=introduction-overview-zosmf">z/OSMF</a> and <a href="http://zowe.org/">Zowe</a>. That led to me getting involved with Zowe and other modernization projects. Last year I moved to the Netherlands, where I now work at Cognizant attending to the financial sector.</p><blockquote><strong>“When you find something that you’re passionate about, you have to make it work — you have to make it fit into your agenda.”</strong></blockquote><h4>Q: What got you interested in platform modernization?</h4><p>I am patient with z/OS, but I also have some criticism. We have good hardware, but I think we need to adapt and explore other technologies and tools to make us better. What really got me interested was seeing other people exploring all the possibilities out there with cloud and other platforms, and yet no one in the mainframe community was using them!</p><h4>Q: You engage a lot with the mainframe community. What motivates you to be so active?</h4><p>The feeling that you’re making a difference for someone. I started doing some presentations that helped some people, and that was the best feeling. I also helped organize meetup groups in Brazil, and that helped new professionals find their first jobs and helped them grow. Those are the kinds of rewarding things that motivate me to be part of the community. When you find something that you’re passionate about, you have to make it work — you have to make it fit into your agenda.</p><h4>Q: Do you consider yourself to be a mainframe influencer?</h4><p>Yes, but I didn’t start with that intention. It was something that just happened!</p><h4>Q: What are some highlights from your work as a mainframer?</h4><p>One of the things I like the most is that no matter how long you’ve been working on this platform, there is always something to learn. There is always something new that will bring new sets of challenges. Even people who have worked on this platform for over four decades often face new challenges.</p><h4>Q: What would you say to the mainframe community about the benefits of choosing and using a range of tools?</h4><p>Explore on your own. See what opportunities you have and what possibilities are out there. Fit some exploration time into your daily activities. Try new things and present the results to your peers and the community; this is how new opportunities start to happen. I didn’t have a platform where I could play without worrying about what I was doing, but that didn’t stop me from exploring. I joined IBM’s <em>Master the Mainframe</em> course (now called <a href="https://ibmzxplore.influitive.com/">IBM Z Xplore</a>), and I mentioned this at conferences. People started noticing my activity on LinkedIn, and that’s how I landed in my current role. Now I have a lot more freedom to lead and make decisions about which tools to use and what to explore next.</p><h4>Q: How do you make the business case for more mainframe investment?</h4><p>In previous roles that was definitely a challenge. But the feeling I get now is that some customers are more open and willing to put more things on the mainframe. Some companies are starting to get people together to try new automation. For example, I’m currently working on a project that involves automating the SSL certificate management process from creation to deployment. It started on z/OS, but we’re using the same tool to bring our automation to other platforms, such as Azure. These are the kind of projects that drive mainframe investment.</p><figure><img alt="Front left angle of IBM z16 mainframe in the manufacturing lab" src="https://cdn-images-1.medium.com/max/1024/1*quvQq3xdhcW_Fen-wgJ2QQ.jpeg" /><figcaption>The new IBM z16 Mainframe embraces the hybrid cloud, AI, security, and open source</figcaption></figure><h4>Q: Have you sensed resistance from other mainframers around new technologies or embracing the hybrid cloud?</h4><p>This culture varies a lot because many people who’ve worked on mainframes for a long time can be resistant to change. The idea is that if something’s working, why should we change it? But it’s different at my current company. I’m seeing more incentives for trying to change things. We provide access to new tools. We have Zowe, Ansible, and Python, for example, and have people in squads from multiple teams exploring new automation opportunities on z/OS.</p><blockquote><strong>“By automating, you save time for things that will really bring value to you.”</strong></blockquote><h4>Q: What would you say to members of the community who are hesitant about using or contributing to open-source projects?</h4><p>Participating in the community is what took me to where I am now. It helped my development and my learning. Participating and contributing with others is how we help each other learn and find solutions.</p><h4>Q: With the many options for tooling available, what attracted you to Ansible?</h4><p>I decided to try Ansible when I started on the platform, and it was really quick to get something working. The learning curve was really nice. It took about two or three weeks of learning, and I got some help from the Ansible for IBM Z team. I decided to write a playbook and found it was really easy. Now I’m working on Mainframe Modules, and about 20–30% of the project is already on Community Modules.</p><h4>Q: What made Ansible so easy to pick up?</h4><p>It has a good community and good documentation. I came from JavaScript and I was more used to JSON than YAML. In the beginning, it was strange working with YAML syntax, but now I get it and I like YAML.</p><h4>Q: Is there anything missing for Ansible for IBM Z to thrive?</h4><p>More community. When I see other communities, they are active on social media. When someone starts on a project, they post a public question, so that they can learn with other people. They are more connected through web channels and have contact with more people to learn the technology. I think we still need to grow in this area.</p><h4>Q: You’ve used JCL, REXX, and custom scripting. Now you use Ansible, too. Has this affected your organization’s automation strategy?</h4><p>We’re focusing on Ansible as the main tool for automation projects. We decided this because it’s simple to maintain and easy for new team members to learn. Plus, we can use Ansible with other programming languages and tools. For example, you can take advantage of existing JCL or REXX assets, but you can start new projects with something newer. And it doesn’t stop there; there are other cloud migration projects that are using Ansible as the main tool. At my company, several people who are fascinated with Ansible and who are willing to learn are starting to work together.</p><h4>Q: Has Ansible been valuable to you personally in terms of projects, products, and technology direction?</h4><p>Absolutely. By automating, you save time for things that will really bring value to you. And just recently I was approached by a team that was working on an Azure migration project, and because of my knowledge of Ansible, they came to me for help. This was not a z/OS project, but it provided me with some great experience and visibility across my organization.</p><h4>Q: How do platform-agnostic technologies help the next generation of mainframers?</h4><p>It makes it easier for new team members to get started because they can focus on what’s important. They can learn concepts and the platform instead of specific interfaces.</p><h4>Q: What value have you seen from working in a hybrid environment?</h4><p>You can put things together and take the best from each platform. For example, it’s easier to keep code in git than in other source code managers, and you can access repositories on multiple environments, such as Azure or z/OS.</p><h4>Q: What do you envision for the future of mainframe automation?</h4><p>Today, many community members think that because the mainframe has the best hardware, no one can successfully migrate workloads to other platforms. But in our hybrid world, we need more agility. I think mainframers are starting to see the importance of using more automation tools, programming languages, and open-source options. This lets you use the tools that you really like, which can bring out better work. In the future, people will do this even more because it is needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OYujjKiBD5UGYKCjvpqHWg.png" /><figcaption>Ansible for IBM Z documentation, and the IBM Z trial provide the best space for hands-on learning</figcaption></figure><p>This article is part of the Ansible for IBM Z User Spotlight. Read our other installments:</p><p>👉 <a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-ipek-dedekoy-3d60c9156eed"><strong>Ansible for IBM Z: User Spotlight Series — Ipek Dedekoy</strong></a></p><p>Stay up to date with our community by joining the IBM Z &amp; LinuxOne community <a href="https://community.ibm.com/community/user/ibmz-and-linuxone/groups/topic-home?CommunityKey=ce54fe94-0145-4832-a0ef-4ea81d6062cc">topic group for Ansible for IBM Z</a>.</p><p>Here are some additional resources if you are interested in automating with Ansible for z/OS:</p><ul><li><a href="https://www.ibm.com/support/z-content-solutions/ansible/">Ansible Content Solutions</a></li><li><a href="https://docs.ansible.com/ansible/2.9/modules/modules_by_category.html">Ansible Documentation</a></li><li><a href="https://ibm.github.io/z_ansible_collections_doc/index.html">Ansible Collections</a></li><li><a href="https://ibm.biz/BdfakN">Ansible for IBM Z videos on IBM Media Center</a></li><li><a href="https://survey.alchemer.com/s3/6603851/Ansible-for-IBM-Z-Survey-NPS-Survey">Give us your feedback on our Ansible for IBM Z Survey</a></li></ul><p><em>Special thank you to @dan.jast1 and Nate Myers for your hard work and contributions to this article.</em></p><p><em>The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28683569cc1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/ansible-for-ibm-z-user-spotlight-series-bill-pereira-c28683569cc1">Ansible for IBM Z: User Spotlight Series — Bill Pereira</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>