<?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 Chris Hardtman on Medium]]></title>
        <description><![CDATA[Stories by Chris Hardtman on Medium]]></description>
        <link>https://medium.com/@hardtman?source=rss-a3256aef4303------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*PFRHt1TkcNcj-N1QoUsN2g.jpeg</url>
            <title>Stories by Chris Hardtman on Medium</title>
            <link>https://medium.com/@hardtman?source=rss-a3256aef4303------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:17:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hardtman/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[A New Design-Centered Meeting Framework: Better Capture the Product Design Narrative]]></title>
            <link>https://medium.com/newyorkpublicradiodigital/a-new-design-centered-meeting-framework-better-capture-the-product-design-narrative-6552cca904f7?source=rss-a3256aef4303------2</link>
            <guid isPermaLink="false">https://medium.com/p/6552cca904f7</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking-culture]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Chris Hardtman]]></dc:creator>
            <pubDate>Wed, 14 Jul 2021 21:06:36 GMT</pubDate>
            <atom:updated>2021-07-14T21:19:15.057Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xGEjs29DDfokBifztJFxfw.png" /><figcaption>Illustration by Oleg Shcherba from <a href="https://icons8.com/illustrations/">Ouch!</a></figcaption></figure><p>As New York Public Radio, like many other organizations, have shifted to working remotely over the last year, we saw a need to rethink how we collaborate in order to increase productivity. Like many design teams before COVID-19, we already used tools like Figma and Miro that made passive or asynchronous communication possible but once we removed the in-person aspect, a few things changed.</p><h3>What does the format convey?</h3><p>When we were at the office, it was easy to convey the fidelity of the design work using the format and wording of the ask itself. For instance, a product designer may have asked a product manager and an engineer to pop by her desk to review some work-in-progress. Not only was the Figma wireframe clearly a work-in-progress, but the environment (casually stopping by someone’s desk to look over their shoulder) also conveyed this message.</p><p>Fast forward well into remote-only world and a casual work-in-progress convo could easily get confused with a higher-fidelity demo (where there is less time to integrate feedback) because we are now using the same format for both informal and formal meeting-types, <strong>Zoom</strong>. We noticed that even if we stated the agenda in the meeting invitation, we received feedback from teammates who they felt like they were being brought too late into the design process and weren’t sure of their role or the kind of feedback expected. What went wrong?</p><h3>Create clarity</h3><p><strong>How do we clearly communicate the product design narrative?</strong> How do we let the broader product development team know where we are? The product design narrative includes every step of the design process: discovery, research, product strategy, direction, frameworks, tactics, and most importantly, conclusions (what did we solve for? why?). A lot of the conclusions or solutions part of the narrative is represented in Figma or in Storybook (the <a href="https://storybook.nypr.digital/latest/index.html?path=/story/welcome-introduction-to-radial--page">Radial design system library</a>) or in Slack threads. How do we better document this narrative in one place? Is one-stop communication even feasible?</p><blockquote>The product design narrative includes every step of the design process: discovery, research, product strategy, direction, frameworks, tactics, and most importantly, conclusions (what did we solve for? why?).</blockquote><h3>Map it out</h3><p>Where were we having conversations? Where were decisions being made? Who needs to weigh in? If we have the same kinds of meetings, can we create some shape or clear structure around this? Without removing the creative (conversation) aspect?</p><p>After bringing up the topic with the design team, one person surfaced <a href="https://uxdesign.cc/silent-design-critiques-making-your-design-team-more-effective-afafa4561e82">Figma’s meeting framework</a>. We liked how this provided some definition to the type of design meetings but didn’t handcuff the team to a particular process. <strong>We too wanted to create something malleable as design is about exploration. </strong>The Figma model was great inspiration.</p><p>In October of 2020, we ran a design team workshop using Miro and Zoom to determine how we communicated, why, with whom, roles, responsibilities and pain points. We framed it as “An open-ended dialogue and workshop on design team responsibilities, communication, tools and process connectivity.”</p><p>We started with some free-form post-it dropping. Which started to take shape when we themed the notes, and then noticed that we could sequence the themes or major needs in an order that aligned with the design team process. Notice that we were able to put shape around the pain points (on salmon-colored stickies) and sequence things in an organic fashion.</p><figure><img alt="Screenshot of our Miro board workshopping" src="https://cdn-images-1.medium.com/max/1024/1*3P6JZxPktyaUyWpuaoPL0Q.png" /></figure><p>We were then able to map out the types of design conversations we were having, again with pain points (on salmon-colored stickies). I’m purposely not showing the detail but the visual is good context because you’ll see how much structure we dissect from this later.</p><p><strong>The key elements</strong> we were able to parse out from this step were:</p><ol><li>Discussion format</li><li>Participants (who and why)</li><li>Input types desired</li><li>Expected outcomes</li><li>Timing (when to run the meeting during our process)</li></ol><p><strong>Which provided a holistic view of design-related conversational inputs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSb-CWMDpdLSW8iORknFvA.png" /></figure><p><strong>Pro design leader tip:</strong> Keep these design-related conversations very open-ended or risk losing the chance to capture ideas from your team . Beware of narrowing scope too early! Designers need room to explore, test, see and then re-check themselves to arrive at a collaborative solution.</p><h3>The new design meeting framework</h3><p>We took the team’s knowledge share and synthesized the insights into a framework. One that brought together the 5 key elements (format, participants, inputs, outcomes, timing) from the last step. When would we run a pair design vs a check-in vs a review?</p><p>We begin the design conversation with a Kick Off to discuss a project vision and get early alignment with other disciplines. This could also be the pre-work to product discovery. From there, we typically run Pair Design sessions to ideate with a small group where we create visual artifacts or discuss data and research. Check-ins are informal and a space to discuss work in progress and keep everyone in the loop. Reviews are done with design management to ensure that the work is aligning with product and design strategies. The key difference between Check-in and Review is that the Review is where the design head provides detailed design direction, normally in a group setting so everyone can benefit from the feedback.</p><p>This meeting framework was then shared with the broader digital team. It was helpful to align on expectations, vernacular (check-in vs review), and when these meeting types would pop up during the product design process. <strong>This framework is meant to be a guidepost and not something we dictate from project to project. It’s need-based and built for clarity.</strong></p><p>One of the biggest benefits to the team and our process has been the ability to capture the product design narrative. This narrative includes the reasons why we made certain decisions, our design direction, how it may have adjusted over time and product descriptions. It is the responsibility of the design team to capture the feedback and outcomes that shape the product design narrative and this framework makes it clearer on when to do that and why.</p><h3><strong>Our new framework 🎉</strong></h3><figure><img alt="Meeting framework that was mapped out in Miro" src="https://cdn-images-1.medium.com/max/1024/1*Og3tPOpsMYOO9opQlAoBuA.png" /></figure><p><strong>The meeting types</strong></p><p><strong>Kick-off</strong>: Discuss scope of project and initial design approach. Input: Information from other disciplines in order to accurately give design estimates. Why: To create a shared understanding of goals, success criteria, stakeholders, and set roles &amp; responsibilities. When: Beginning of process.</p><p><strong>Pair Design</strong>: Ideate with small group to gather ideas and synthesize together. Some sketches, inspo or data gathering may be done ahead of time to get convo rolling. Input: Deep, expansive dive on subject. Keep open ended to gather as much info and ideas as possible. Why: Flexible and hands-on meeting required to get early alignment and inputs. When: Very early in design process.</p><p><strong>Check-in</strong>: Informal conversation to discuss work in progress, show options, get other’s perspectives (e.g. Dev, Product, Content, Marketing) and to keep everyone in the loop. Input: Focused input on artifact type and within scope and theme. Looking for others to provide input from their expertise. Feedback is recorded. Why: To discuss the design work and get feedback in order to move project forward. When: Middle of process.</p><p><strong>Review</strong>: Design direction and alignment with design management. Small meeting within the design team to discuss work, strategy, output and next steps. Why: To ensure that the work is as expected, meets goals, adheres to design direction and standards. To get feedback and approve work as complete or design done. When: Beginning, middle and/or end of process.</p><p><strong>Demo</strong>: Formal presentation with scrum, digital, cross-department or external groups to share work. Input: Feedback is welcome and captured (but not integrated) as this meeting occurs late in the product design process. Why: To ensure a shared understanding of what is going to be built. When: Nearing the end of the process.</p><p>So what replaced that use-case of people popping by a designer’s desk? The check-in. This can happen asynchronous or synchronously (typically over Zoom) but it is now clear that there is a space to discuss work in progress AND a place where <strong>the designer is responsible for capturing feedback, mentioning that feedback in the project Slack channel and showing up at a later point with visuals that reflect team inputs.</strong> The goal is to ensure that everyone on the Digital team knows the progress stage of the work, who to go to with questions or suggestions, and where to access the latest visual files or mockups.</p><p>One final takeaway from this process and our lived experience working remotely for more than a year: <strong>you have to communicate MUCH more often in a remote-only environment. Repeat yourself.</strong> Threads disappear in Slack and in email, bookmarks to links you need can get lost. You have to capture that product design narrative and share it with the team. The NYPR design team utilizes radical transparency in everything we do. We ask the team to over-communicate. That can be a burden and you do need to set limits (and time off of Slack) but in a remote-only world, giving your teammates a heads up, note-taking and providing minutes in an open channel, all lend themselves to a more informed and better-aligned team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6552cca904f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newyorkpublicradiodigital/a-new-design-centered-meeting-framework-better-capture-the-product-design-narrative-6552cca904f7">A New Design-Centered Meeting Framework: Better Capture the Product Design Narrative</a> was originally published in <a href="https://medium.com/newyorkpublicradiodigital">New York Public Radio Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where Engineering and Design Overlap]]></title>
            <link>https://medium.com/newyorkpublicradiodigital/where-engineering-and-design-overlap-e37f4e7bf83e?source=rss-a3256aef4303------2</link>
            <guid isPermaLink="false">https://medium.com/p/e37f4e7bf83e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[nypr]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Chris Hardtman]]></dc:creator>
            <pubDate>Tue, 19 May 2020 19:22:22 GMT</pubDate>
            <atom:updated>2020-05-19T19:22:22.532Z</atom:updated>
            <content:encoded><![CDATA[<h3>How We View the World</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2V-3TUb-CycPUla_CvCUhA.jpeg" /><figcaption>Illustration by Chris Hardtman. Photo by Retha Ferguson/Pexels.com</figcaption></figure><p>Engineering and design have many commonalities such as the way we see a broad set of inputs and connectivity that inform our creative solutions. Engineers have to see what came before to understand what they are doing so they can anticipate (where possible) what is to come. Similarly, designers have to look through an analogous lens when we create design patterns that support good UX and make additions or adjustments that affect a larger system, product, or user experience.</p><p>In terms of thinking broadly, Jim Jazwiecki, New York Public Radio’s Head of Engineering says that</p><blockquote><em>“Engineering is creative problem solving. What are the constraints that I have to build around? Is there an elegant way to do this? Is there a way to make it central to build off of that constraint?”</em></blockquote><p>Sounds familiar if you are a designer. For example, we look for ways to simplify the building blocks in our design systems so that they are reusable. In order to do so, we consider their functionality, how brand-aware they need to be, how an end-user will be affected by adding or adjusting certain elements, and if the underlying system patterns make sense. We do this even if we have to design a “simple” email collection component.</p><p>Engineers and designers are sculptors with digital tools. <a href="https://www.goodreads.com/quotes/457177-design-is-not-just-what-it-looks-like-and-feels">Apple’s Steve Jobs</a> famously said <em>“design is not just what it looks like and feels like. Design is how it works.”</em> Jazwiecki gets to an artful point with</p><blockquote><em>“Understand the negative space around a problem. It’s not just about this exact statement (problem). Where is the question coming from? What can we extract from this? A designer or engineer needs to extract that understanding to solve the problem.”</em></blockquote><p>We need all digital disciplines working collaboratively to craft quality products.If everyone is doing their job, we should see the world like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*voqri0amupRYykQhrYJkNg.jpeg" /><figcaption><strong>Engineering (black) and Design (red) look broadly while Product (brown) helps with focus</strong> / Chris Hardtman</figcaption></figure><h3>Engineering &amp; Design: Breadth and Depth</h3><p>Case in point, you are working on your design system and you have identified multiple platforms that the system could live on. Design and engineering go into research and POC mode while product sets up a <a href="https://medium.com/product-gyaan/swot-analysis-c226f5b1ad52">SWOT analysis</a> to compare the options in a highly organized way. Product wants to help narrow in on a solution, yet at the same time, engineering and design work on creating a <a href="https://www.nngroup.com/articles/5-steps-service-blueprinting/">service blueprint</a> to better understand connectivity to other platforms, people, and systems. Engineering looks at the code base and dependencies, and together with design, they knock around the tooling possibilities. Is there a way to create better design and development environment connectivity?</p><p>Design and development are in a flow. First, they look broadly, across systems or components in order to see the right place to solve. In doing so, they look for connectivity and patterns around a system to ensure that they do not miss any key dependencies that, if not considered, may make or break a part of the system. Teams need the space and time to explore and iterate. As <a href="https://www.pentagram.com/about/paula-scher">Paula Scher</a> says in the <a href="https://www.netflix.com/title/80057883">Netflix series, <em>Abstract: The Art of Design</em></a>, <em>“You have to stay in a state of play to design. Otherwise you can’t make or do anything.”</em></p><p>Too many constraints can suffocate ideas. To reiterate Jazwiecki, Engineering is about creative problems solving. His team looks for smart ways to make what they build reusable, in an elegant or sometimes unconventional way.</p><p>While design and engineering are working together, product tries to provide clarity around what is doable with the given resources, keeps everyone on their toes with how the work connects back to larger goals, and uses other techniques to determine the best use of effort.</p><p>Since engineering and design are <strong>creative problem solvers</strong>, they can see problems through a similar lens, but at the same time, with the benefit of using their discipline’s unique eye.</p><blockquote><em>“Some of the best projects I’ve been on have been about understanding the non engineers”</em></blockquote><blockquote><em>“The best possible world is when engineering and design can process together”</em></blockquote><p>says Jazwiecki.</p><p>When design and engineering process information together, lean on each other for expertise, and look broadly to come to an agreement on where to focus, no one has to play catch-up.<strong> The sparks, the magical ah-ha moments and momentum can happen in unison, as a team.</strong></p><p>Let us know what you think. Please leave comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e37f4e7bf83e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/newyorkpublicradiodigital/where-engineering-and-design-overlap-e37f4e7bf83e">Where Engineering and Design Overlap</a> was originally published in <a href="https://medium.com/newyorkpublicradiodigital">New York Public Radio Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>