<?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 Matthew Cunningham on Medium]]></title>
        <description><![CDATA[Stories by Matthew Cunningham on Medium]]></description>
        <link>https://medium.com/@cunningdesign?source=rss-926fbe74b720------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Exlg3ViXtG25mhPExCjRBg.png</url>
            <title>Stories by Matthew Cunningham on Medium</title>
            <link>https://medium.com/@cunningdesign?source=rss-926fbe74b720------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:03:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cunningdesign/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[How to Embrace the Democratization of AI UI Tools]]></title>
            <link>https://cunningdesign.medium.com/how-to-embrace-the-democratization-of-ai-ui-tools-c94f6ebee5d5?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/c94f6ebee5d5</guid>
            <category><![CDATA[ai-ux-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Wed, 14 Jan 2026 20:49:31 GMT</pubDate>
            <atom:updated>2026-01-14T21:43:18.751Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hVeic8yU6bEjJqO3mblwRQ.jpeg" /><figcaption>Image Credit: <a href="https://unsplash.com/@theshubhamdhage"><strong>Shubham Dhage</strong></a></figcaption></figure><p>I recently watched a Product Manager use a generative AI UI tool to “design” a complex dashboard in under thirty seconds. On the surface it looked beautiful. It had the data visualizations, a clean layout, and a perfectly balanced color palette. It was also, from a usability standpoint, a complete disaster.</p><p>We have entered an era where high-fidelity design has become a commodity. Tools like Figma Make, loveable and UX Pilot have effectively collapsed the distance between a raw idea and a polished artifact. This is often framed as the “democratization of design,” which sounds lovely in a keynote speech.</p><p>Accessibility is not the same as expertise, and speed without accuracy is just a faster way to arrive at the wrong solution.</p><p>When we give everyone a paintbrush, we get more art. When we give everyone a tool that generates production-ready UI, we get a massive influx of “generic designs” that look like “validated designs” but typically don’t address user problems or end-to-end workflows well.</p><p>The code world already learned this lesson. AI can write a script in seconds, but that doesn’t mean the code is secure, scalable, or even functional in a complex environment. Design is facing its own “Vibe Coding” moment. To survive this, design leaders need to stop worrying about the tools and start obsessing over the rules.</p><h3>The Problem of Premature Fidelity</h3><p>In a traditional workflow, fidelity acts as a signal of progress. A wireframe says let’s talk about logic. A high fidelity mockup says let’s talk about the look and feel. I’ve <a href="http://In a traditional workflow, fidelity acts as a signal of progress. A wireframe says let’s talk about logic. A high fidelity mockup says let’s talk about the look and feel. To keep this alignment from breaking, I religiously use the 10/50/99 model to set clear expectations when getting user feedback. This framework ensures we are talking about the right things at the right time. AI flips this logic on its head by delivering 99 percent fidelity when the project is still at the 10 percent thinking stage.">implemented the 10/50/99 model </a>for decades to set clear expectations when getting user feedback. This framework ensures we are talking about the right things at the right time.</p><p>AI flips this logic on its head by delivering 99 percent fidelity when the project is still at the 10 percent thinking stage. This creates a dangerous illusion of completion. Stakeholders see a polished screen and stop asking the hard questions about user flow or edge cases. They assume the thinking is done because the pixels are pretty.</p><p><strong>The Danger:</strong> As noted by the <a href="https://www.nngroup.com/articles/aesthetic-usability-effect/"><strong>Nielsen Norman Group</strong></a>, this effect can “mask usability problems and prevent issues from being discovered during usability testing.” If users are blinded by aesthetics, stakeholders who often have less UX training, are even more susceptible.</p><p>What this really means is that <strong>“Fidelity Must Match Maturity”</strong> rule is backed by 30 years of behavioral science. By forcing stakeholders to look at “ugly” wireframes during discovery, you are actually protecting them from their own psychological biases and ensuring that the product’s foundation is built on logic, not just “pretty pixels.”</p><h3>The Framework</h3><h4><strong>1. Drawing the Scope Boundary</strong></h4><p>The first rule of the AI UI era is simple: <strong>AI tools generate UI; they do not define UX.</strong></p><p>Your company guidelines must explicitly state that while AI is great for exploring layouts or generating pattern options, it is never allowed to define product strategy or user journeys. An AI output is a draft artifact. It is a starting point, not a decision. If leaders don’t draw this line in the sand, teams will naturally default to the path of least resistance, which usually involves letting the machine make the choices.</p><h4><strong>2. Tying Fidelity to Phase, Not Role</strong></h4><p>We need to stop people from jumping the gun. One way to do this is to enforce fidelity based on the project phase.</p><p><strong>The Discovery Phase is for Learning:</strong> During this stage, high-fidelity UI should actually be discouraged. If an AI tool produces something that looks finished, it should be stripped back to a low-fidelity representation. Why? Because a finished look kills the desire to experiment.</p><p><strong>The Define Phase is for Alignment:</strong> Here, you use AI to generate variants, not solutions. You are testing for comprehension and flow.</p><p><strong>The Deliver Phase is for Execution:</strong> This is the only place where “the look” matters. This is where the design system acts as the ultimate gatekeeper.</p><h4>3. Research as the Hard Gate</h4><p>Speed is a double-edged sword. Just because you can design a feature in an afternoon doesn’t mean you should build it by Friday.</p><p>As UI becomes cheaper to produce, research becomes your most valuable quality control mechanism. Guidelines should require human interpretation of every finding. AI can summarize a user interview, but it cannot empathize with the frustration in a user’s voice. Research must remain a manual, intentional gate that prevents “pretty” but “useless” features from reaching production.</p><h4>4. The Design System is Not Optional</h4><p>AI tools love novelty. They love to invent new buttons and unique spacing logic. This is the enemy of a cohesive product.</p><p>Your guidelines must treat the design system as a non-negotiable boundary. If the AI spits out a component that doesn’t exist in your library, it gets tossed. Allowing AI to bypass your design system is a fast track to a fragmented user experience. It’s not a tooling issue; it’s a leadership failure to maintain standards.</p><h4>5. Who Interprets the Feedback?</h4><p>Inexperienced people are now empowered to collect feedback on AI prototypes. That’s great for speed, but dangerous for accuracy and understanding.</p><p>Feedback without experienced interpretation is just noise. Design decisions require trained judgment to separate “I don’t like this color” from “This layout violates a core usability heuristic.” Your policy should ensure that while anyone can gather input, the interpretation of that data remains a collaborative effort involving design, research, and content expertise.</p><h4>Operationalizing the Policy</h4><p>Guidelines fail when they live in a doc instead of the workflow. The simplest move is to embed AI UI rules into the same gates work already flows through.</p><ul><li><strong>Stage gates:</strong> Discovery requires a problem statement, assumptions, and low fidelity flow. Define requires a prototype plus a learning goal. Deliver requires design system compliance, accessibility checks, and evaluative research sign off.</li><li><strong>Minimum evidence:</strong> One page that captures what user problem is being solved, what was tested, what changed, and what remains risky. If it is not written down, it is not done.</li><li><strong>Decision rights:</strong> Anyone can generate screens. Not everyone can ship decisions. Define who can approve design system exceptions, waive research, or introduce new patterns.</li></ul><h4>Moving from Policing to Purpose</h4><p>This article isn’t about being the “design police.” It’s about providing the guidelines to ensure these tools can be used at scale.</p><p>When output is cheap, judgment becomes the most expensive asset in the room. The organizations that thrive won’t be the ones with the best prompts or the fastest to a prototype. They will be the ones with the clearest rules.</p><p>When AI removes the friction of creation, leadership must supply the discipline of intentionality. We do that by doubling down on rigorous user research and the expert judgment of experienced designers. That is how good design survives at the scale of AI driven UX.</p><p>To help other teams navigate this shift, I am sharing two ready to use policy templates. My goal is to help teams embrace these tools in a way that is actually scalable and ensures high quality results for everyone involved.</p><h4>Available policies</h4><p><a href="https://docs.google.com/document/d/e/2PACX-1vRCD7GfOXMNsKK6t7Koxki9Y7temU_Mj38TQ-iGahbFDknaqkj-WCYva6WwISwSi4-0JEice27B4Zd9/pub">AI UI Policies</a> | <a href="https://docs.google.com/document/d/e/2PACX-1vRzyTGgDHowjPzbLoBetnHc3BXqoLXVLcivdQbKOmY7C3sEAhccgz8SCvr_-1boCqSMRp-Rq_Ung5bo/pub">AI UI Governance Checklist</a></p><p>If you found this article helpful or you have implemented similar policies, I’d love to hear from you.</p><p>Special thanks to <a href="https://medium.com/u/afa718982d08">Greg Storey</a> for the editorial review.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c94f6ebee5d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Questions Product Designers should ask during an interview.]]></title>
            <link>https://cunningdesign.medium.com/questions-product-designers-should-ask-during-an-interview-890cf9395de7?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/890cf9395de7</guid>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Thu, 24 Mar 2022 15:46:02 GMT</pubDate>
            <atom:updated>2022-03-24T15:46:02.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Interview questions for designers" src="https://cdn-images-1.medium.com/max/1019/1*Iv9lZ5z00WGUGsshsn9J0Q.png" /><figcaption>Credit: undraw.co</figcaption></figure><p>Below is a bank of questions I reference during interviews. Obviously, not all these questions can be asked, but since each interview is unique, having a reference-able list is always helpful. Feel free to use these as a guide or inspiration when interviewing.</p><p><em>Tip:</em> When interviewing, do the research on the company. Look for their vision and mission statements. Look at Glassdoor, see their ratings, review the feedback. Doing research on a company is mandatory to ensure you can get behind their purpose — even with well established brands.</p><h4>General questions</h4><p><em>Where I start when first interviewing, usually in screening calls. These questions give insight into others perceive working there. How others ‘perceive’ working at a company is the closest you get to actually knowing what the culture is like.</em></p><ul><li>Do you love working here, why?</li><li>What are some of [company name] UX principles</li><li>What is [company name] mission?</li><li>How is [company name] going to win?</li><li>Who owns the Vision?</li><li>Whats one thing about the culture here you like the most?</li><li>Can you explain to me what [Company Name’s] Vision means to you?</li><li>How does the organization support your professional development and career growth?</li><li>Is risk-taking encouraged, and what happens when people fail?</li><li>What role does [company name] values play in aligning teams on outcomes?</li><li>What’s one thing you would change about the company if you could?</li><li>In what ways does the company practice user centered methodologies?</li></ul><h3><strong>Role focused questions</strong></h3><p><em>Next, I start here when talking with designers and design management. These questions give insight into how ‘design’ is done at the company.</em></p><ul><li>What are the main challenges this role will face?</li><li>What one of the biggest areas on improvements you think this role could help with?</li><li>When is design brought into the decision making process on a new idea or feature?</li><li>How do you measure quality?</li><li>How do you deal with consistency and scale?</li><li>What are the main challenges you deal with as a manager on a day to day basis?</li><li>What’s the best part about being a designer at [Company Name]?</li><li>Is there a culture of critique? If so, what is it like?</li><li>How is work shared/viewed with members of the Product team?</li><li>Do you have any design tenets? If so, what are they?</li><li>What’s one of the biggest hurdles the design team would say they have?</li><li>How do you deal with consistency across product teams?</li><li>How do you communicate designs/progress up the chain?</li><li>How does work get prioritized?</li><li>How do you ensure your staff has autonomy, purpose and mastery?</li><li>Do you feel empowered to stop ship something? If so, can you give me an example?</li><li>Do you feel other members of the product team (Engineering and Product) are bought into the “design” process?</li><li>What are some of the cool projects you’re working on today?</li></ul><h3>Research focused questions</h3><p><em>These questions give insight into how Design works with Research. How research measures work and the means to which they conduct user research.</em></p><ul><li>Where does research come into the process?</li><li>Is Research centralized or de-centralized?</li><li>Who assigns priorities for Research?</li><li>When do you use Attitudinal vs. Behavioral?</li><li>How do you balance the qualitative with quantitative?</li><li>How does the team measure success?</li><li>Who conducts usability tests?</li><li>Who defines metrics for success?</li><li>Who manages access to customers or users?</li><li>Do you use NPS and if so, what are your thoughts on that?</li><li>How often do you playback to execs on findings?</li><li>Who creates the end to end vision of what the users wants/needs?</li><li>How do compromises work between date driven results vs actually solving user problems?</li></ul><h3>For Product Management</h3><p><em>These questions give insight into how product management is done and how they perceive working with design.</em></p><ul><li>How are priorities define and communicated?</li><li>How do you measure quality?</li><li>What do you see is UX’s role?</li><li>What are some of your biggest challenges?</li><li>What analytic tools do you use to track Product goals?</li><li>What would you like to see from the person taking this role?</li></ul><h3>For Development</h3><p><em>These questions give insight into how development is done and how they perceive working with design.</em></p><ul><li>How do developers perceive the design team?</li><li>How does dev collaborate with Designers?</li><li>What about the technology excites you?</li><li>What are some of your biggest challenges?</li><li>What would you like to see from the person taking this role?</li><li>What’s the #1 thing you’d improve working with the Design Team?</li><li>How often do features get shipped?</li><li>Can you do A/B testing?</li><li>What analytic tools do you use to track user interactions?</li></ul><p><em>Working with Dev/Prod is all about relationships — establishing trust, collaboration and healthy debate.</em></p><h3>Fun questions</h3><p><em>Probably some of the most important questions you can ask.. These questions will give you a sense of the personality of the individual(s) you will be working with.</em></p><ul><li>What’s the last song you listened to?</li><li>What would your direct reports say is the best thing about working for you?</li><li>What’s the last book you read?</li><li>If you had to pick one, which one would it be and why?</li><li><em>New York Penthouse off 5th ave</em></li><li><em>Beach front chalet off French Rivera</em></li><li><em>Log cabin in the Swiss Alps</em></li><li><em>Country House tucked away in Stowe, VT</em></li></ul><p>Like them, have suggestions? I’d love to hear your feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=890cf9395de7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Budgeting for Creative Departments]]></title>
            <link>https://medium.com/design-bootcamp/budgeting-for-creative-departments-95b8843e24b6?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/95b8843e24b6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-operations]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Wed, 24 Mar 2021 20:21:13 GMT</pubDate>
            <atom:updated>2021-03-26T14:21:50.121Z</atom:updated>
            <content:encoded><![CDATA[<h3>Budgeting for creative departments</h3><p>A helpful start on budgeting for in-house creative departments.</p><figure><img alt="Picture of an abacus" src="https://cdn-images-1.medium.com/max/1024/1*ECayPFera84sZU7ReCAOYQ.jpeg" /><figcaption>Like the abacus, budgeting can look confusing but once understood can be a powerful tool for creative departments to leverage</figcaption></figure><p><strong><em>Disclaimer</em></strong></p><p><em>The following information targets in-house corporate design leaders, managers, or operations who have departments for which they have financial accountability. This article does not cover the operational costs needed to maintain a creative company or agency as an entity. Topics like human resources, recruitment, insurance, taxes, rent, marketing, etc., are not covered.</em></p><p><em>That being said, whether you are new to design management, manage a small team, or manage multiple teams, the following information will help you with planning and budgeting in a corporate environment.</em></p><h3><strong>Why read this?</strong></h3><p>I currently run a multidisciplinary UX department while managing a multimillion-dollar budget. I’ve managed a few budgets like this in my career and have learned a lot. Each time I build a team, whether from zero to thirty or go from one department to five, it all centers around a solid budget. I quickly learned an easy-to-read budget that communicates the financial requirements, meets business objectives and results in getting what you need to run a successful team.</p><p>If you get nothing else from this article, know that your team’s long-term success comes down to funding. Whether it be for a short-term project or building a world-class UX organization, funding is at the core. The better you demonstrate how <em>your costs</em> align to priorities, the more success you’re likely to have. And that translates into having the right designer ratios, the right tooling, and the right people-development needed to sustain a high-performing team.</p><h3><strong>Why a Budget for Creative Teams?</strong></h3><p>I’m noticing more and more designers are tasked with managing departments or whole business units. The so-called “seat at the table” allows designers more prominence and influence within companies. This often comes with additional responsibilities that aren’t part of our core skill set. Aside from people management, designers are being asked to plan and manage a wide variety of budgetary elements including salaries, technology, tools, professional development, and other operational aspects of a business.</p><p>I don’t know about you but I didn’t go to business school. So the question becomes, how do you plan, budget, and communicate your intent while interacting with other departments in a way we‘re not familiar with? The departments needing to approve and interact with your budget range from Human Resources, Recruitment, Finance and IT. All of which have their standard ways of operating and communicating. So, where do you start?</p><h3><strong>Ready.. Set.. Budget!</strong></h3><p>The first step to managing a creative business unit is having a solid budget plan! Outside of people management, fiscal management is quickly becoming the responsibility of Design leaders. However, you won’t easily find a budget specifically for creative teams. At least I couldn’t.</p><p>Therefore, I’m <a href="https://docs.google.com/spreadsheets/d/1geONb9foNnZPNpp1XzpD1zjs1hakcQAm7IFZ18ISQDo/edit?usp=sharing"><strong><em>attaching my budgeting template</em></strong></a><strong><em> </em></strong>to help get you started.</p><p>I’ve used this template for years. It covers a wide range of topics needed to plan, manage and budget to just about any creative department. There are simple formulas and pre-populated data to help keep things simple and tidy. The template and categories aren’t exhaustive and may need tweaking based on how your company operates, but in general, it’s a good place to start.</p><p>A well-planned budget affords me greater success in building and maintaining creative teams than almost any other skill I’ve developed as a leader. When it comes down to it, showing the business you understand how finances work and the costs associated with running a business, quickly becomes critical in getting the approvals you need.</p><p>As a designer, spreadsheets drive me nuts and were one of the hardest things to accept about managing creative departments. Over the years, I’ve learned spreadsheets are an effective way to plan and project costs across multiple departments. It seems spreadsheets are the universal language of business operations. If you’re not a wiz at spreadsheets, don’t panic, here’s a simple overview of <a href="https://www.excel-easy.com/examples/budget.html"><em>some basic formulas</em></a><em> to help you out</em>. These formulas are simple enough to learn and will help make your budgets easier to manage. You should also get used to the idea of the higher up in management you go, the more time you’ll be utilizing spreadsheets.</p><figure><img alt="picture of the spreadsheet in Google Sheets" src="https://cdn-images-1.medium.com/max/1024/1*dAwZOfI5OXl9bAOSaUR7Gg.png" /></figure><p>In the template, there are four tabs with subcategories. The tabs are as follows:</p><ul><li>People</li><li>Technology</li><li>Professional Development</li><li>Travel and Entertainment</li></ul><p>I’ve broken down the tabs and categories to help make them easier to understand.</p><h3>The first tab: People</h3><figure><img alt="Picture of the tab labeld People." src="https://cdn-images-1.medium.com/max/1024/1*LDeEEdDcViYP981t-H88KA.png" /></figure><p>This tab is where you break down the aspects of a ‘resource’ within your department. People are usually the #1 cost for a company. The better you are at budgeting and communicating your people needs the better results you’ll have. There are many complexities around budgeting for people, and you’ll use them to plan and communicate your intent for the coming fiscal year. And because hiring is hard, it’s good practice to have a plan that you can work towards. It may not be 100% accurate but it acts as a good roadmap.</p><p>The People Tab includes the following categories:</p><ul><li><strong>Owner </strong>— This is the person responsible for this individual. This could be you, your manager, or your manager’s manager. Just depends on how many levels your organization has.</li><li><strong>Priority</strong> — What is the priority for this resource? Ex: High, Med, or Low</li><li><strong>Position / Title</strong> — This is the role you have or intend to fill Ex: designer, researcher, etc.,)</li><li><strong>Grade</strong> — This can be levels or some other experience classification. Grade refers to a number or some other classification in seniority of a Position/Title.</li><li><strong>Salary</strong> — The salary of the individual. This is important because it will help you break down the costs of a person as it pertains to your overall budget.</li><li><strong>Bonus</strong> — If applicable, will affect the total cost of a salary.</li><li><strong>Location</strong> — Depending on whether or not you have international teams, this could have tax and/or currency implications.</li><li><strong>Start Date</strong> — This is when a requisition opens and when the associated cost hits your budget.</li><li><strong>FTE (full-time employee) / Contractor </strong>— This communicates to Finance whether or not this will be a one-time or recurring cost. FTEs have different total cost impacts relative to contractors.</li><li><strong>CapEx / OpEx</strong> — Depending on how your company categorizes resources, you may need to specify whether or not this resource is assigned to Capital Expenditures or Operational Expenditures. <em>Here’s a quick </em><a href="https://www.investopedia.com/ask/answers/042415/what-difference-between-operating-expense-and-capital-expense.asp#:~:text=An%20operating%20expense%20(OPEX)%20is,for%20accounting%20and%20tax%20purposes."><em>overview of the difference</em></a><em>. I won’t go into the details of how these work but be sure to ask your Finance partner what the difference is. It’s worth taking the time to understand the difference.</em></li><li><strong>Initiatives</strong> — These are the initiatives, products, or projects this resource will be allocated toward.</li><li><strong>Description</strong> — The justification for the role, which includes a description of the role relative to the initiative to which it’s being allocated.</li><li><strong>Justification / Details — </strong>The “why” this role is needed.</li><li><strong>Timeline</strong> — A salary is typically prorated based on the hiring date. If you have a designer with an annual salary of $45,000 starting on June 1st, the impact to your hiring budget is approximately $22,500. This is because the salary won’t hit your budget until the hire date, 7 months into the calendar year. Timelines really help you plan more accurately to an overall cost.</li></ul><p>This section isn’t exhaustive but, in general, should be enough to communicate what you’re planning with your Finance and Human Resource departments.</p><h3><strong>The second tab: Technology</strong></h3><figure><img alt="Picture of the tab labeled Technology" src="https://cdn-images-1.medium.com/max/1024/1*V0YOhXdAknVABi68D1ADOQ.png" /></figure><p>This category breaks down all the technology or tools your team will need. The caveat to this is some companies have their internal IT departments manage the cost themselves. While this is common, IT often charges back the cost to the department using it. Where design often requires specialized tools, this tab will help you plan for the associated costs. Besides, we all know designers love trying new tools, and this section can also be used to account for the cost of ‘testing’ novel technologies.</p><ul><li><strong>Owner — </strong>To whom the tooling belongs. This is needed when you have multiple disciplines like Research, Content Writers, or some other unit other than Design.</li><li><strong>New Purchase / Renewal — </strong>Indicate if this a new purchase or a renewal.</li><li><strong>Supplier / Event — </strong>Indicate the name of the supplier.</li><li><strong>Description — </strong>The justification for the cost of new technology, which includes who it’s for and why it’s needed.</li><li><strong>Priority — </strong>Indicate the priority of the tool relative to your business<strong>.</strong></li><li><strong># People Dependent — </strong>The number of people who will be using the tool/technology.</li><li><strong>Timeline </strong>— This helps Finance and/or IT understand when costs will hit the budget.</li></ul><h3><strong>Third Tab: Education</strong></h3><figure><img alt="Picture of the tab labeled Educatioin" src="https://cdn-images-1.medium.com/max/1024/1*PiIty-B-8AAujUDLT6R50Q.png" /></figure><p>This section is where you plan for your team’s professional development, or as I like to call it, “Education.” I’m a huge believer in ‘sharpening the saw’ and I make sure there’s an allocation in my budget to support those who want to learn. The costs for professional development may be managed outside your department but it’s a good idea to plan out any foreseeable costs. While this may be overkill, it’s better to have the information and not need it. My only caveat with education is individuals must share what they learned so that others may benefit from the knowledge gained.</p><ul><li><strong>Quarter</strong> — Indicate which quarter education will hit.</li><li><strong>Benefit</strong> — Also known as the “Why,” this is the benefit to the company. Given this is paid for by the company, it’s best practice to ensure the company gets value from the training.</li><li><strong>Type</strong> — Indicate the type of development, from Conferences to Team Training to Academic Courses.</li><li><strong>Registrant or Speaker</strong> — Conferences only. This may adjust the cost depending on whether someone is attending versus speaking.</li><li><strong>Link to Conference or Course</strong> — Provide a link to the conference, training, or course.</li><li><strong>Travel Required</strong> — If applicable; some conferences are virtual.</li><li><strong>Need ancillary event/dinner</strong> — Indicate the cost associated with meals.</li><li><strong>Need full sponsorship dinner</strong> — If sponsoring an event, this cost could be much higher than individual costs.</li><li><strong>Estimated Registration Fee</strong> — Costs to attend.</li><li><strong>Estimated Expenses (airfare, hotel, meals, etc.)</strong> — This cost varies depending on how your company estimates expenses. Ask your Finance partner if they allocate general costs for education, travel, and per diems, as they should have these numbers.</li><li><strong>Total Estimated Costs</strong> — The total cost for education.</li></ul><h3><strong>The fourth tab: Travel &amp; Entertainment</strong></h3><figure><img alt="Picture of the tab labeled Travel and Entertainment" src="https://cdn-images-1.medium.com/max/1024/1*9UIGcdnX0x_LaRF0c9xy_g.png" /></figure><p>This is often overlooked but is a very important part of any good departmental budget. Next to people, travel can be one of the highest costs a company incurs. And depending on how your team is structured and how many people are in your department, you may need to make frequent trips. Things like onsite customer visits to conduct user research or with a 100% virtual team, you’ll likely need to get everyone together once a year. There are many reasons to ensure you have a travel budget. And although “entertainment” may sound superfluous, it’s an imperative allocation. Entertainment contains money for paid lunches, team swag, and a manager’s discretionary fund to empower s/he to do something nice for the staff.</p><ul><li><strong>Owner</strong> — Indicate who owns travel or entertainment.</li><li><strong>Expense</strong> — Indicate the type of expense, such as Customer visits, Team building, team collaboration, SWAG, etc.</li><li><strong>Expense Type</strong> — Indicate whether this is OpEx or CapEx. This may not be relevant to some but worth having just in case.</li><li><strong>Supplier / Event</strong> — This indicates the identity of any/all 3rd party vendor(s).</li><li><strong>Description</strong> — The justification and use of the cost for travel and/or entertainment, which includes…</li><li><strong># People Dependent</strong> — The number of people this cost impacts.</li><li><strong>Timeline</strong> — Indicate when the costs will hit the budget.</li></ul><p>For entertainment, it’s best to first talk with your finance partner to see if you can get an average cost per headcount. In doing so, it’ll help you understand the general cost per headcount and how much to allocate. For example, if you have 10 designers and want to budget $100 per quarter for team outings. Simply add up the cost per person, per quarter, and calculate it that way. That results in $10 per person per quarter or $40 per year per person. Therefore you need $400 for the entire year. Looking at it as a total cost helps you allocate the right amount so don’t have to come back later and ask for more money. And be sure to factor in any new headcount you may be hiring too.</p><p>The same goes for travel. Typically Finance departments have an average cost for travel. It should include the average cost of flights (both domestic and international), hotels, and per diems. Once you have those numbers, you can multiply them by the number of people that need to travel. <em>Note: </em>travel can quickly become expensive so be sure you understand the need for travel before arbitrarily adding to your budget. I typically budget quarterly and assume about one-third of my team actually needs to travel frequently. The rest is ad hoc. Or if you’re a 100% remote team (not just because of COVID), I highly recommend getting everyone together at least once a year.</p><h3><strong>In Conclusion</strong></h3><p>The secret to a thriving and successful creative department is having a well-planned budget. This may sound strange coming from a designer, but I’ve learned over the years that once you have the money to do the things like add headcount, have the right tools in place, and the ability to develop your staff, is, without doubt, a critical part of a highly functioning team. I can’t stress this enough. A well-planned budget keeps you from having to continually ask for money after the budget has been agreed upon. And that rarely works out.</p><p>It’s also worth noting that even if you are not required to submit a budget, I strongly encourage you to ask if you can participate in the discussion around financing or see what costs are being associated with your team. As design leadership continues to move up in company ranks, there will come a time when you’ll be asked to provide a budget. And now at the very least, you have a headstart. Remember, he/she who has the best plan usually wins.</p><p>Obviously, there’s a lot more to ‘running’ a creative department than just having a stellar budget. And if there’s interest, I can write about the other aspects of what it takes to run a high-performing creative department. Thanks again for reading and happy budgeting!</p><p>Special editorial thanks to <a href="https://medium.com/@fangmarks">Matt Fangman</a> and <a href="https://medium.com/@blanchflower">TJ Blanchflower</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95b8843e24b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/budgeting-for-creative-departments-95b8843e24b6">Budgeting for Creative Departments</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The agile designer series — daily stand up]]></title>
            <link>https://cunningdesign.medium.com/the-agile-designer-series-daily-stand-up-681097499b24?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/681097499b24</guid>
            <category><![CDATA[agile-ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Sat, 21 Oct 2017 18:42:55 GMT</pubDate>
            <atom:updated>2021-03-26T14:55:36.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Graphic with title of The Agile Designer Series — the Stand-up." src="https://cdn-images-1.medium.com/max/1024/1*0DcITg925uX3lu_dxWy_mw.png" /></figure><p>When instituting Agile within my Design teams, the first question I got was “where do we start”?</p><p><em>Prologue: The following article is targeted at Product Designers wanting to understand Agile and how to apply Agile methodologies into their work process. Although many of the recommendations can be applied to other design industries and disciplines.</em></p><h3>What is Agile?</h3><p>Agile isn’t a new word nor is it a new concept, especially within the Software industry. In fact, Agile can be found not only in the software industry but also in personal growth and non-technical industries like Healthcare and Sales. But I often find it’s not clear what Agile really means to people. It’s simple really, Agile is like Yoga. Yoga is a philosophy and there are many types of Yoga practices like Hatha, Ashtanga, and Bikram to name a few. When you say “I practice Yoga” people who know say “Oh, what kind?”</p><p>Saying you practice “Yoga” only speaks to the philosophy, not the practice. True practitioners understand the difference between philosophy and practice. It’s important to understand Agile has many types of <a href="https://en.wikipedia.org/wiki/Agile_software_development#Agile_practices">practices</a> and it’s those practices that define Agile. Be sure to understand the difference between philosophy and practice.</p><h3>Why is Agile important?</h3><p>This article doesn’t go into why agile is important instead this article focuses on getting started with Agile Scrum. To learn more about why Agile is important and understanding its benefits, <a href="https://medium.com/@cunningdesign/the-agile-designer-series-why-agile-for-design-9ebc39f8c2fe">read this article</a>.</p><p>Implementing Agile for Designers, a.k.a. Agile UX, is really important because it keeps us from going down the rabbit hole too far or spending too much time on designs without knowing if we’re really solving problems or not. Agile UX teaches us how to break problems down, focus our work efforts, and prioritize what needs to get done so we can design better products and services.</p><figure><img alt="Graphic showing traditional ux timelines" src="https://cdn-images-1.medium.com/max/946/1*PJQoR9-aRSlgADtaa_8UNw.png" /><figcaption>Traditional UX model</figcaption></figure><p>At first, Agile is hard for most Designer and Design organizations to understand because we tend to work on visionary concepts first or build a Journey Map or lots of upfront user research. In fact, with Agile, Designers have to balance the vision work with the tactical work. Learning how to break concepts, problems, or ideas down into small, medium, and large chunks is one of the hardest skills to learn.</p><p>Once you’ve learned how to break things down, the work then becomes more focused and ultimately gives Designers the ability to pivot and change as needed. Agile also allows Designers to “focus” on specific problems and when implemented right (Agile UX), it gives Designers the time needed to fully understand the problems they’re trying to solve.</p><figure><img alt="Graphic showing peaks and valleys representing how to work in short sprint cycels." src="https://cdn-images-1.medium.com/max/946/1*66O-0Uwu79EDpcAHflvtGA.png" /><figcaption>Agile UX model</figcaption></figure><h3>Where do I start?</h3><p>When instituting Agile within my Design teams, the first question I got was “where do we start”? Starting an Agile practice is akin to starting Yoga. When start a new Yoga practice you won’t be able to do all the poses and that’s fine. Just stat with one. So I start with something simple, <strong>the daily stand-up</strong>.</p><p>Whether you practice Scrum, Kanban, or any other type of Agile methodology, the daily stand-up (oftentimes called Daily Scrum) proves time and time again to be one of the most valued parts of implementing an Agile practice. Stand-ups are quick and easy to set up, they don’t take a lot of effort to do and they’re highly effective. They are a great way to introduce a team to Agile.</p><figure><img alt="Picture of designers standing in front of a monitor during a video call" src="https://cdn-images-1.medium.com/max/1024/1*bSKSzu2irrWFFmn17SDqUg.png" /><figcaption>Typical design standup. Notice the “remote” designer with video feed</figcaption></figure><h3>The Setup</h3><p>By focusing on what each person accomplished yesterday and will accomplish today, the team gains an excellent understanding of what work has been done and what work remains. The daily scrum meeting is not a status update meeting in which a boss is collecting information about who is behind schedule. Rather, it is a meeting in which team members make commitments to each other.</p><p>To run an effective stand up there are a few key concepts to understand. To start, someone needs to “lead” the meeting to ensure it’s run correctly and efficiently. This person is sometimes known as a “Scrum Master” but try to avoid this type of nomenclature as it leads to single responsibility and detracts from the self-regulated spirit of Agile. Start out by assigning one person per week to lead the meeting. They will be in charge of keeping things moving and ensure any blockers are addressed. Switch out the lead responsibility to each member of the team on a weekly basis. This helps distribute responsibility across the team and helps gain experience running a stand-up.</p><p>Next, it’s very important to <em>define an agenda and be clear about its purpose</em>. When sending out the calendar invite be sure to list specifically what the rules and goals are. And finally, make sure it’s at the right time. Having them too early or too late in the day can result in either low attendance or missed opportunities to resolve issues.</p><p>When implementing a stand up follow these simple rules:</p><ul><li><em>Keep it to 15 minutes or less</em></li><li><em>Be clear about the agenda</em></li><li><em>Don‘t solve problems, just inform</em></li><li><em>Keep it short and simple</em></li><li><em>Designate someone a different person each week to lead the meeting</em></li></ul><h3>The Rules</h3><p>To run an effective stand-up, some rules need to be clearly established early. Start with a daily fifteen-minute meeting first thing in the morning or at a time that best fits your structure. At first, this may seem excessive or even feel like it’s adding more meetings to your daily routine, but done right will be one of the most effective meetings you have all day. When setting up the meeting be sure to clearly set expectations and define the Agenda. During the meeting each person will say the following three things:</p><ul><li><em>What I did yesterday</em></li><li><em>What I’m doing today</em></li><li><em>Am I blocked?</em></li><li><em>Fun statement (optional)</em></li></ul><p>It’s that simple. Any discussions outside of the above topics need to be taken “offline”. The point of this meeting is to identify issues or “blockers” before they impede progress. This meeting is not to get into discussions around problems.</p><h3>The Scrum Master</h3><p>Every week someone needs to lead the meeting. This person is known as the Scrum Master. Scrum Masters are in charge of running the meeting, ensuring the sprint board is up to date, and follows up on post-meeting actions should there be any. They also ensure everyone shows up on time. The Scrum Master has other duties besides running the stand-up, but for now, just focus on running the stand-up.</p><p>And at the end of the week, the acting Scrum Master gets to choose a new Scrum Master to run the meetings.</p><p>Tip: Stand-Ups don’t have to be all cut and dry. When beginning these meetings try adding a fun statement at the end of the update. A fun statement is set by that week’s Scrum Master. Adding these in helps keep people engaged with the process and it’s fun!</p><p>Some “fun” topics to consider:</p><ul><li><em>What was the last thing you listened to?</em></li><li><em>Recommend UX/UI websites</em></li><li><em>Recommend podcasts</em></li><li><em>Worst “Dad” joke</em></li></ul><h4>Example emails and calendar invites</h4><p>Here is an example email introduction introducing the stand up:</p><p><em>Team, As we move towards practicing Agile I’m taking a first step by implementing a daily stand-up. This meeting will ensure everyone is aware of what others are doing and no one is blocked or cannot move forward with their work. Any conversations related to an update can be followed up after the meeting or “offline”.</em></p><p>Here is an example calendar invite for the stand up:</p><p><em>I’d like to meet once a day to discuss progress being made by the team. This meeting will last only 15 minutes and focus only on updates. Please come prepared to discuss the following:</em></p><ul><li><em>What you did yesterday</em></li><li><em>What you did today</em></li><li><em>Are you blocked</em></li><li><em>What’s your best dad joke</em></li></ul><h3>The Participants</h3><p>Who should join your stand-up? This depends on how your design team is set up, but all team members are required to attend the stand-up. Anyone else (for example, a departmental VP, a Salesperson, or a product owner from another project) is allowed but is there only to listen.</p><p>If your team is part of an existing multi-discipline team then everyone on that team is required to attend. Most likely your development team is already doing some kind of stand-up. If you aren’t attending them, start! Be sure to communicate your interest in participating before attending. It’s important to understand the structure of the meeting so you can be seen as a value not a hindrance.</p><p>If you don’t have access to an existing stand-up (scrum meeting), start having a stand-up within your own team. Practice having the meeting, go overwork, and simply getting used to the process. It’s also a good idea to include your Product owner and development leads (if available) is optional.</p><figure><img alt="Picture people standing together in a semi-circle." src="https://cdn-images-1.medium.com/max/1024/1*r6yoHPB2HVFzCpNcc2mOFQ.png" /><figcaption>Stand Up should include Design, Development and Product Owners</figcaption></figure><h3>Things to Consider</h3><p>As I mentioned earlier, stand-ups are a great way to dip your toe into practicing Agile. The key to any successful agile practice is being open to what works and what doesn’t. I encourage you to experiment and always get feedback.</p><p>When dealing with remote teams, I strongly encourage including a video chat as the video tends to help keep remote individuals engaged.</p><p>I often get asked if my team physically “stand up”. Yes, we really stand up. I’ve found standing helps to keeps individuals focused. Furthermore, this is a closed laptop meeting. That means no computers are allowed other than the one showing the video feed or showing the product backlog.</p><p>If you’re using a process management tool like Trello or Jira be sure to have it up on a screen when individuals are going talking. Walking through your product backlog increases tracking and managing work better. Some teams find it helpful to talk through their product backlog before moving on to the next update.</p><p>Tip: During the meeting make sure everyone gets in the habit of writing their update down on paper. This makes people come prepared and helps move the meeting along quickly.</p><h3>What’s Next?</h3><p>I’d love to hear from you on any experiences you have with implementing or practicing Agile methodologies within your design team or organization.</p><p>Remember to <strong>be patient but persistent — </strong>being patient is key. Make sure to be patient with your team as they “figure” things out, but also be persistent. Be there to answer questions and to provide support when things go awry!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=681097499b24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating an Experience Roadmap]]></title>
            <link>https://cunningdesign.medium.com/creating-an-experience-roadmap-2b1f706d7ba3?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b1f706d7ba3</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Mon, 02 Oct 2017 02:13:41 GMT</pubDate>
            <atom:updated>2017-10-02T02:20:52.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Nh5-GxHwdHxUP-hj_87fw.png" /></figure><p>One of the most requested items from product teams are Product Roadmaps. Everyone from CEOs, Marketing and even customers want to know when a feature or functionality is going to be released. They make executives feel like they understand when things are going to be delivered, Sales likes them because they can use them as leverage in deals, and they strive to give predictability to customers.</p><p>But one thing you can count on - they always change. Most of the time product owners “guess” or SWAG at what can be delivered. Too often I’ve seen Product Managers create slides or fancy Gantt charts mapping out release dates and dependencies. Product Roadmaps are like goals. Everyone hopes to achieve them, maybe even exceed them, but in the end we typically end up adjusting them for one reason or another and delaying the release.</p><p>Because Roadmaps change frequently it’s difficult for teams to structure their work based on a single direction especially one that’s continually moving or changing. Its like trying to hit a moving target that you know is going to move once you set aim. But more importantly, it makes creating a consistent and seamless user experience very challenging.</p><p>So, how can designers create a consistent and compelling user experiences with such volatility? Well, there’s a solution — <strong><em>Experience Roadmaps (ExR)</em></strong>. ExRs are a way for teams to plan their work in concert with Product Roadmap. ExRs help teams stay focused, create stability and help drive a consistent user experience. They also ensures user problems are being solved and limits the amount of UI churn.</p><h3>The Concept</h3><p>There are three key elements to creating a solid ExR. The North Star, The Lighthouse and The Flashlight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvLkRZomq2at-sbXMf8tDA.png" /><figcaption>North Start, Lighthouse and Flashlight concepts</figcaption></figure><p>One can generally understand their meaning (using light as a metaphor), but let me explain. North stars were used by sailors for centuries to help them navigate across vast oceans and for long distances. Stars are far away and yet are a constant, predictable source of truth for direction. In the UxR, the North Star represents the overall vision for your product or your long term direction.</p><p>Keeping with the light metaphor, Lighthouses were used as navigational aids and to warn boats of dangerous areas. They are much closer than stars, but still provide guidance. Thus Lighthouses should be used for near term efforts like epics, features or releases. You can have many Lighthouses for one North star.</p><p>Finally the Flashlight. Flashlights are held by individuals, provide light on relatively small areas and are typically short range. Flashlights represent user stories, bugs and other tactical or short term items. Flashlights typically comprise most of your sprint’s workload.</p><h3>Implementation</h3><p><em>Caveat — obviously every idea or concept should be validated or based on user research, market research and/or A/B testing. ExRs should include research and testing time.</em></p><p>When creating a ExR designers should consider the end result of their ideal user experience.<em> </em>Because user experiences aren’t linear and can often times involve many decisions or dependencies, ExRs should reflect user flows needed to complete end-to-end scenarios. Don’t think of them as releases or feature based but more what a user needs to do to complete a task or set of tasks.</p><p>At my work we use the concept of “Hills” for our long term or Big ideas. Although I like this concept, I feel Hills can confuse the the Designer on their single vision and can lead to focusing solely on a single Hill while ignoring the other Hills that comprise the total vision or outcome.</p><p><strong>When defining your North Star consider the following:</strong></p><ul><li>Create a single mission your Product does or is</li><li>Who are the people you’re solving problems for?</li><li>What are the “key” end to end workflows?</li><li>Why are these scenarios important?</li><li>What does your product <em>not do?</em></li></ul><p>For defining end to end user flows I highly suggest using the Jobs to Be Done method as defined by <a href="https://www.amazon.com/dp/0814438032/ref=cm_sw_r_cp_dp_T1_OyXpzbB37YFHH">Anthony W. Ulwick</a>.</p><p><strong>When defining your lighthouse consider the following:</strong></p><ul><li>Break down the flows into sizable chunks as defined in Lean UX written by <a href="http://leanuxbook.com/">Jeff Gothelf and Josh Seiden</a></li><li>Think of single workflows</li><li>How would these roll up into a single North Star</li><li>Are there any technical limitations?</li><li>Are there any known timelines or deadlines?</li></ul><p><strong>When defining your flashlight consider the following:</strong></p><ul><li>What tasks need to be done to complete them? Research, testing, validation, etc..</li><li>What dependencies do you have?</li><li>Who would work on these?</li><li>What persona’s are being address?</li><li>What one problem are you solving?</li><li>How do these lead into the Lighthouse?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-51XbypqB-MRk4MDW4B4uw.png" /></figure><p>With these items defined, the team now has a clear vision of where they’re going regardless of how they get there. Your team will thank you, your end product with be better and you’ll have a better sense of direction.</p><p>A really good place to define these three concepts is in a “Product Summit”. Product Summits include everyone who is responsible for delivery, marketing and selling of the product. In a workshop setting and using design thinking principles, the team works to define the North Star, Lighthouse and even some flashlights (Marketing and Sales should have users stories too!) documents. Preferably these “alignment” sessions happen quarterly or even semi-annually.</p><p>Product Summits are also a good way to get everyone on the same page with direction. Remember “A unified vision is better than a single great one” and while this responsibility typically falls with the Product Owner it’s the Designer’s responsibility to create it for the user!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b1f706d7ba3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design and Engineering’s sprints, do they need to be the same?]]></title>
            <link>https://cunningdesign.medium.com/design-and-engineerings-sprints-do-they-need-to-be-the-same-b9f3f5aac39c?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9f3f5aac39c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Mon, 05 Sep 2016 21:29:19 GMT</pubDate>
            <atom:updated>2016-09-05T22:06:14.709Z</atom:updated>
            <content:encoded><![CDATA[<p>I often get asked if a Design team’s sprint have to be on the same schedule as their Engineering teams. The easy answer is - yes, ideally it would be great, but what if it’s not possible? What if your development team works on a different cadence or uses a totally different agile model?</p><p>Actually, this isn’t a bad thing and here’s why.. Design and Engineering processes are fundamentally different. There — I said it. Don’t get me wrong, it’s possible for both disciplines to work together, but Design and Engineering workflows are different, sometimes very different. It’s like the Yin and Yang.</p><p>This Chinese philosophy describes how opposite or contrary forces are actually complementary, <a href="https://en.wikipedia.org/wiki/Interconnected">interconnected</a>, and interdependent in the natural world. Similarly, Design and Engineering are interconnected and yet have very different workflows. But somehow both work together to deliver an end result. However, that doesn’t mean they have to adhere to each other’s schedule.</p><p>If your development team works on their own sprint cycle here are some tips on how to work within that constraint.</p><h4>Key Steps</h4><ul><li><strong>Pick a discipline. </strong>Make sure your or your Design team is practicing some form of Agile UX. Whether it be Scrum, Kanban or Scrumban, you must have a consistent work life cycle. I suggest Scrum which you can <a href="https://medium.com/@cunningdesign/the-agile-designer-series-choosing-the-right-agile-practice-75de3e882d51#.2vqemk76r">read more here</a> as to why.</li><li><strong>Prioritized Backlog.</strong> Make sure you have a backlog of work including epics and user stories.</li><li><strong>Consistent sprint cadence</strong>. I suggest 2 week sprints as it tends to be just enough time to make progress and yet still allows for pivoting without too much loss of work.</li><li><strong>Bi-monthly sprint planning meeting</strong>. At the beginning of each design sprint meet with the Developer Lead and Product Manager to review your team’s weeks prioritized work. Be sure to communicate when work is going to be ready for “development”, work that needs to be sized or work that’s coming down the pipe.</li><li><strong>Daily Stand-ups</strong>. If your team isn’t doing these start now. I address the benefits of stand-ups in my other article “Choosing the right agile practice”.</li><li><strong>Sprint Demo Day</strong>. At the end of every sprint, demo the work that was done. Highlight any work that’s ready to be “delivered” and needs sizing.</li><li><strong>Communicate your plan</strong>. Always communicate your plan and what deliverables the sprint will yield. Knowing what’s coming is critical for both parties to plan accordingly.</li></ul><h4><strong>Key concept</strong></h4><p>Just because you work on 2 weeks sprints doesn’t mean you delivery work that’s ready for development at the end of every sprint. Sometimes research or getting user feedback can take several sprints. For instance, the graphic below illustrates a monthly sprint cycle for an Engineering team and a two week sprint cycle for a Design Team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eGJdZBsmCyFV9sVJJT-JQQ.png" /><figcaption>“Off” Cycle Sprints</figcaption></figure><p>During Sprint Planning and Demo Day the sizing and delivering of design assets can be coordinated with Product Management and Engineering.</p><p>In addition, even when both teams are on the same sprint cycle delivery of design assets may vary depending on when work is ready.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_kvWY_ajbwlPMXSunSogw.png" /><figcaption>“On” Cycle Sprints</figcaption></figure><p>Again, communication and planning of the delivery is key in coordinating the flow of work between the two teams.</p><h4>In Conclusion</h4><p>It’s ok for design teams to run on their own cycles as long as communication is part of the plan. Like the Ying and Yang - each team depends on each other and needs clear communicate on what they’re delivering and when.</p><p>Done right, both teams can actually work fast, produce high quality products, and still work how they want to!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9f3f5aac39c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Agile Designer Series - Choosing the Right Agile Practice]]></title>
            <link>https://cunningdesign.medium.com/the-agile-designer-series-choosing-the-right-agile-practice-75de3e882d51?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/75de3e882d51</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile-ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Sun, 12 Jun 2016 23:03:14 GMT</pubDate>
            <atom:updated>2016-06-12T23:13:48.793Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytGm3xMrIMT5CKW167O95w.png" /><figcaption>The Agile Designer Series — Choosing the Right Agile Practice</figcaption></figure><p><em>Prologue: The following article is targeted for Product Designers wanting to understand Agile and how to apply Agile methodologies into their daily process. Although, many of the recommendations can be applied to other design industries and disciplines.</em></p><h3>The many flavors of Agile</h3><p>There are many many types of Agile methodologies such as Scrum, Kanban, Extreme Programming, Crystal, Dynamic Systems Development Method, and Feature-Driven Development to name a few. I would encourage you to research them so you can better understand which practice fits your needs. For the purpose of this article I’m only covering Scrum and Kanban as I have experience with those.</p><h3>Scrum</h3><p>With Scrum, the product is built in a series of fixed-length iterations called sprints and work is pre-defined in what are called “user stories” that are in priority order as defined by the Product Owner. Each user story is kept in what’s known as a Product Backlog.</p><p>During each “sprint” the teams decided on how many users stories they think they can complete within the fixed timeline. Furthermore, during the Sprint no new work can be added. Work is basically set and committed to. Any new work or issues that arise automatically get put into the Backlog where they will be “groomed” and prioritized relative to current priorities by the Product Owner.</p><h3>Benefits</h3><p>One of Scrum’s main benefits include working from a prioritized set of user stories within the Product Backlog. The backlog is a prioritized feature list containing short descriptions of all functionality desired in the product. The backlog is mostly comprised of User Stories but larger efforts are grouped into Epics.</p><p>To be clear, a Product Backlog <strong><em>is not the solution</em></strong> rather it’s the user problem, feature or functionality that’s desired in the product. Because design is responsible for creating the visual and user experience, solutions should be written as part of the requirements.</p><p>One of the key components to Scrum are the meetings. To most Designers meetings really means one thing — time suck. Meetings can be the death of productive designing because we need large swaths of time to think through problems and meetings tend to break that up. Since implementing Scrum with my design teams, we’ve reduced the number of meetings with shorter, more focused and more productive ones.</p><p>Scrum has a set number of meetings that bring structure to each sprint.</p><p><strong>Sprint planning</strong> — The sprint planning meeting involves pulling items from the backlog into the sprint and prioritizing the user stories that will be carried out during the sprint.</p><p><strong>Story grooming — </strong>Story grooming meeting involves sizing and understanding what requirements are and typically happen before planning and usually with key decision makers.</p><p><strong>Daily stand-up</strong> — The daily scrum or stand-up meeting includes a short daily meeting where each member of the team briefly shares what they are working on. The daily stand-up typically lasts no more than 15 minutes.</p><p><strong>Sprint demo</strong> — The Sprint demo meeting reviews the team’s progress after each sprint.</p><p><strong>Sprint retrospective</strong> — The retrospective meeting discusses ways to improve the process.</p><h3>Drawbacks</h3><p>Some see the Scum meetings as too invasive. In addition, a good many software companies are moving towards continually delivering features. For instance, Amazon is known for releasing features every five minutes and Facebook developers are expected to release code into production on their first day. With Scrum framework that would be hard to do. Pivoting or continuously delivering new features constantly is where Scrum would not be a good method.</p><h3>Kanban</h3><p>The Kanban methodology is way less structured than Scrum. Essentially teams work from a prioritized backlog of stories and there typically isn’t a specific timeline like Scrum. In Kanban, you organize your work on a Kanban board. You have columns also known as states, which every work item passes through — from left to right. individuals pull work items through the columns as work progresses. Boards may have various <em>swim lanes</em> — horizontal “pipelines” for different types of work. Typically boards consist of the following pipelines:</p><ul><li>Backlog</li><li>In Progress</li><li>Blocked</li><li>Delivered</li><li>Done</li></ul><p>The basic principle is you move a work item from the “Backlog” into “In Progress”. Work that item until it moves to “Done”. Blocked is there in case progress get’s “Blocked” by a dependancy. Once you’ve completed a story you move to the next highest priority story, rinse and repeat. Obviously, each team can set up it’s own pipeline as needed, but basically that’s how it works.</p><p>For every column (state) on your Kanban board you should define a “Work In Progress” or what’s known as the WIP Limit. The WIP limit tells you how much work items are allowed to be in a certain state at any given point in time. If a state reaches its predefined WIP limit, no new work can enter that state.</p><h3>Benefits</h3><p>Kanban allows for quick, fast and constant iterating on features. Typically teams that have been practicing Scrum and want to move faster use Kanban due to its constant delivery cycles.</p><h3>Drawbacks</h3><p>For design teams straight Kanban can be challenging because it focuses on continual improvement and to some extent feels as if there is “no end in site.” Often times designers benefit from taking time to create a vision or longer term path. Not to say Kanban can’t do this but it’s really geared towards short iterations and constant tweaking.</p><p>That being said, Kanban is a great way to force process management and allows a clear understanding of what’s being worked on and where things may be “blocked”. Kanban boards are one of the most appealing aspects of Kanban and is why so many teams use this method. In fact so many teams love the Kanban board they often times combine Scrum and Kanban into one — ScrumBan.</p><h3>Next steps..</h3><p>When deciding which Agile method to implement for your team, the best advice I can give is to experiment with both Scrum and Kanban. Agile is about adapting to change quickly. For my team we practice what’s known as <strong><em>ScrumBan</em></strong>.</p><p>In my next article I outline Scrumban methodologies and describe how to take first steps towards implementing Agile into your daily design routine. Look for that sometime in July 2016. In the meantime, if you have any questions feel free to ask in the comment section below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75de3e882d51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Agile Designer Series - Why Agile for Design?]]></title>
            <link>https://cunningdesign.medium.com/the-agile-designer-series-why-agile-for-design-9ebc39f8c2fe?source=rss-926fbe74b720------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ebc39f8c2fe</guid>
            <category><![CDATA[agile-ux]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Matthew Cunningham]]></dc:creator>
            <pubDate>Sun, 12 Jun 2016 22:47:57 GMT</pubDate>
            <atom:updated>2016-06-12T23:14:16.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e7iVEwpXEe0ZJTNC7ep4fA.png" /><figcaption>The Agile Designer Series — Why Agile for Design?</figcaption></figure><h4>A practical guide to implementing an Agile UX practice</h4><p><em>Prologue: The following article is targeted for Product Designers wanting to understand Agile and how to apply Agile methodologies into their daily process. Although, many of the recommendations can be applied to other design industries and disciplines.</em></p><h3>What is Agile?</h3><p>Before we get into first steps, it’s important to understand “what” Agile is and “why” it’s important to Product Designers. If you’re in software it more than likely you’ve heard the term “Agile” at some point. It isn’t a new concept, especially within the Software industry, and you may even know someone or been at a company that practiced some type of “Agile” development. In fact, Agile is so prevalent it can now be found in a myriad of other non-technical industries like personal growth, Healthcare, and even Sales.</p><p>For this Article, however, I won’t go too deep into the history of Agile instead I’ll briefly cover the basics. .Back in the 1990’s software companies started noticing too much “lag time” between shipping software and what the market wanted. So much so that this issue became commonly known as “application delivery lag.” In 2001 a group of software developers got together and decided to fix the problem. They wrote what’s known as the “<a href="http://www.agilemanifesto.org/history.html">Agile Manifesto</a>” and thus Agile was born.</p><p>Fast forward to today, integrating Agile within the Design and UX industries is now becoming more widely adopted as the standard way of designing user experiences. <a href="http://www.gv.com/sprint/">Google</a>, <a href="http://www.ibm.com/design/thinking/in-practice/">IBM</a> and other <a href="https://www.nngroup.com/articles/agile-development-and-usability/">thought</a> <a href="https://www.smashingmagazine.com/2011/03/lean-ux-getting-out-of-the-deliverables-business/#lean-ux">leaders</a> are demonstrating the benefits of implementing Agile methodologies into the design process. However, in my experience, actually implementing these methodologies into today’s Product Design team’s can be a daunting and frustrating process. This Article aims at helping you start applying Agile methodologies into your design and/or ux process.</p><h3>Why is Agile important for Designers?</h3><p>Agile for Product Designers or what I call “Agile UX” is important for a couple of reasons and when implemented correctly, Agile UX allows for the following benefits:</p><ul><li>Provides clarity of scope for the Designer and team</li><li>Allows time to “focus” on problems/tasks</li><li>Makes pivoting or changing direction relatively easy</li><li>Eliminates the big design up front (B.D.U.F. ) or Big Bang releases</li><li>Creates organization and structure within the team</li><li>Increases the overall quality of work</li><li>Allows for better visibility with Development, Product Management and Stakeholders</li><li>Satisfaction of getting shit done on a regular basis.</li></ul><h3>Pitfalls of Agile</h3><p>When implementing any process you need to be aware of the pitfalls. Although Agile is great it also has it’s weaknesses. Here are just a few things to consider when implementing Agile. Is strongly recommend you have a mentor or Agile coach available to help navigate you with implementing the practice.</p><p><strong>Agile Mentor or Coach</strong> — Like I said, if you are new to Agile be sure you have a mentor or a coach that can help you with implementing it. Doing it yourself and as a beginner, will cause you and your team to make a lot of mistakes. Although mistakes are fine when starting an Agile practice it will only delay the benefits. And when starting something new, at some point you want to reap the benefits. Having someone help guide you will help minimize the mistakes.</p><p><strong>Get Buy-in</strong> — Make sure to get everyone bought into the process. Literally sit down with your team and discuss wanting to start applying Agile processes. Getting buy-in will also increase the likelihood of successfully implementing Agile.</p><p><strong>Attempting to take on too much</strong> — Take it slow. In later articles I walk through how to start implementing Agile practices. Take it slow and be methodical. I’ve seen teams try to take on too much and end up more frustrated than necessary. Remember, everyone is learning so start small.</p><p><strong>Be patient but persistent — </strong>being patient is key. Make sure, if you’re leading the Agile transformation, to be patient with your team as they “figure” things out, but also be persistent. Be there to answer questions and to provide support when things go awry!</p><h3>What’s Next?</h3><p>The question now becomes <strong>how</strong> and <strong>where</strong> do you start? Which Agile method is right for you or your team? Don’t worry, I got you covered. In the <a href="https://medium.com/@cunningdesign/75de3e882d51"><strong><em>next article</em></strong></a> I cover the types of Agile, I believe, work best for Product Designers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ebc39f8c2fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>