<?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 James Billson on Medium]]></title>
        <description><![CDATA[Stories by James Billson on Medium]]></description>
        <link>https://medium.com/@james_primary?source=rss-5bb90c3b7a9b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qoyXmwEB9q9DCla0vmSGFg.jpeg</url>
            <title>Stories by James Billson on Medium</title>
            <link>https://medium.com/@james_primary?source=rss-5bb90c3b7a9b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:16:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@james_primary/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[May 2020 Release]]></title>
            <link>https://medium.com/primary/may-2020-release-8f81078636cd?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f81078636cd</guid>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Fri, 15 May 2020 01:43:10 GMT</pubDate>
            <atom:updated>2020-05-15T01:43:10.561Z</atom:updated>
            <content:encoded><![CDATA[<p>With the world in the grip of Covid19 🦠, we hope that you are keeping safe and well, and busy. There has never been a better time to hunker down and model your next digital product. The <a href="https://www.primary.app/">Primary</a> team haven’t noticed much change to our lifestyle, we don’t go out much in any case🤓.</p><h3>Customer Journeys — Out of Beta</h3><p>After some feature requests and bug discoveries, Primary Journeys are now out of Beta and part of the app for everyone. Journeys now appear in the share view in the same way that Flows display with an overview followed by the detail stages. They are also in the document view.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ec-L5IpVmr1pG0ZC.png" /></figure><p>​</p><h3>Figma integration</h3><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/42/0*A6MI-jmoBa93oK-L.png" /></figure><p>​</p><p>Finally the much requested Figma integration is available. This allows you to store your Figma Persona Access Token with your Primary account, and then put the Figma URL for a specific page in the Interface details. Click Fetch and your beautiful wireframe is linked and stored in Primary. Because Primary keeps versions of everything you do, the wireframe will only update when you request it.</p><h3>Remote URL for Wireframes</h3><p>Leveraging the Figma integration, you can now link a remote URL to a wireframe. The Fetch function is the same as described above.</p><h3>Slack integration</h3><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*SW5Sd2YFVce6V3cF.png" /></figure><p>​</p><p>Add a Slack webhook URL and your comments will be posted to a per-project slack channel.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*bsKUZeYXtMB3ZUUS.png" /></figure><p>​</p><p>Remember our public roadmap 🗺️ is <a href="https://trello.com/b/XWhPSJ0i/primary-roadmap">here</a> if you want to see what’s in the pipeline. <br>Please feel free to get in contact via the Intercom widget in-app, or send an email to hello@primary.app. Stay agile, people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f81078636cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/primary/may-2020-release-8f81078636cd">May 2020 Release</a> was originally published in <a href="https://medium.com/primary">primary</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[March Release]]></title>
            <link>https://medium.com/primary/march-release-f917efcc3331?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f917efcc3331</guid>
            <category><![CDATA[agile-modeling]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 06:54:09 GMT</pubDate>
            <atom:updated>2020-04-03T06:54:09.649Z</atom:updated>
            <content:encoded><![CDATA[<p>Apologies 🙇🏻for the long time between newsletters, we have been busy working on some great new features as well as a total replacement of our back end API. You can now track what we are up to on the <a href="https://trello.com/b/XWhPSJ0i/primary-roadmap">public roadmap</a> 🛣️. This allows you to see what we are thinking about 🤔, what we are doing, and what’s been recently launched 🚀. This newsletter will provide some background to the stuff in the ‘Done in Last Release’ column.</p><h3>Customer Journeys — Beta</h3><p>We think this is a bold new direction for Primary. Customer Journeys make the connection between business strategy and technical implementation. Design the Journey in Stages, and then create Flows to support the Stages where needed.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i3bTCP4QXTHuNtPE.png" /></figure><p>​</p><p>We don’t normally launch beta features. In this case it changes the new feature changes the top line navigation and so we wanted you to switch over when you were comfortable. We have a mini-roadmap for Journey features. Let us know if there’s something you need it to do. You can turn on Customer Journeys in your Account Settings page.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/0*1ETGewQJqIZ5AMS6.png" /></figure><p>​</p><h3>Re-platform</h3><p>You may not even notice (apart from a couple of glitches), but the entire Primary platform has been rebuilt. This allows access to a newer set of services which underpin our next round of improvements. It has been a long job, and back end development gnomes are having a little rest now. We hope you might notice improved performance, mostly in the form of faster page loads and the odd squashed bug.🐛</p><h3>Forms to Data, and Back</h3><p>When creating Data elements, often they are chiefly generated from user inputs via a form. If you started your model with user interactions, then you might find you have a bunch of Forms that need Data elements to store their inputs. If you started by defining a domain model with Data elements, then often you need Forms to populate them. Enter the Form to Data and Data to Form function.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/0*mhVnTgFOFjHUw7Ie.png" /></figure><p>​</p><h3>Primary in the news</h3><p>Read our article in InfoQ:<br><a href="https://www.infoq.com/articles/application-models-software/">https://www.infoq.com/articles/application-models-software/</a></p><p>Please feel free to get in contact via the Intercom widget in-app, or send an email to hello@primary.app. Stay agile, people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f917efcc3331" width="1" height="1" alt=""><hr><p><a href="https://medium.com/primary/march-release-f917efcc3331">March Release</a> was originally published in <a href="https://medium.com/primary">primary</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[November (almost) Release]]></title>
            <link>https://medium.com/primary/november-almost-release-ff78bde0c47?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff78bde0c47</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Wed, 11 Dec 2019 02:04:49 GMT</pubDate>
            <atom:updated>2019-12-11T02:04:49.179Z</atom:updated>
            <content:encoded><![CDATA[<p>We have combined the two into this not-quite-in-November release. There is still a substantial backlog including the major features mentioned last time. We have a new public issues system and a new website on the way. We’ve also been in the news 📰 with a few mentions of Primary by online publications.</p><p>Let’s get on with the shopping list 🛒of this month’s features:</p><h3>1. Resources element</h3><p>An additional type of element has been added, we have called it a Resource. It’s a little different to the other elements in that it is not something that is used by the modeled app, but rather it contains supporting information for the viewer. A Resource element has a description and a URL, it can be used to point to a prototype or UX assets on a separate system.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/0*YAGrPR7YCvKgnUoe.png" /></figure><p>​</p><p>Let us know if you find it useful.</p><h3>2. Branch icon in Flow Overview</h3><p>We had feedback that once a number of alternate flows is created it gets hard to track where they start from. To fix this we’ve added a neat little branch icon into the Flow Overview, and a menu to jump to the alternate flow. We try to keep the number of alternate flows to a minimum, but we know some of you love using lots of them, so this should make that easier.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/539/0*BmbnO9zPmrrhM2WL.png" /></figure><p>​</p><h3>3. Branch icon in Presentation View</h3><p>Much like the item above, in the Presentation view knowing where branches start was a little problematic, especially if the ‘Step Navigation’ was toggled off. Now an icon shows the branch points, and a menu allows you to select the alternate flows at those points.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*68wNoip6Cn4t60BL.png" /></figure><p>​</p><p>Don’t forget you can turn the step navigation on with Ctrl+/</p><h3>4. Full screen preview</h3><p>Now you can see your interfaces as a full screen preview. Just click the preview in the Element pop-out and you get a zoomable, downloadable view.</p><h3>Issues logging</h3><p>As always we invite you to send in your suggestions for new features or reports of anything that’s a bit whack 🙃. Issues can be logged on the public issues list <a href="https://github.com/primaryapp/primary.app/issues">https://github.com/primaryapp/primary.app/issues</a><br>Releases are now logged in detail here: <a href="https://help.primary.app/release-log/">https://help.primary.app/release-log/</a></p><h3>Primary in the news</h3><p>We had a few mentions in the news recently which is nice:<br><a href="https://www.enews20.com/designing-as-a-team-facilitation-apps-that-make-it-work/">https://www.enews20.com/designing-as-a-team-facilitation-apps-that-make-it-work/</a></p><p><a href="https://techbullion.com/interview-with-james-billson-co-founder-of-primary-app/">https://techbullion.com/interview-with-james-billson-co-founder-of-primary-app/</a></p><p>Please feel free to get in contact via the Intercom widget in-app, or send an email to hello@primary.app. Stay agile, people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff78bde0c47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/primary/november-almost-release-ff78bde0c47">November (almost) Release</a> was originally published in <a href="https://medium.com/primary">primary</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[August Updates and Planned New Features]]></title>
            <link>https://medium.com/primary/august-updates-and-planned-new-features-9ac5a895de36?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ac5a895de36</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-flow]]></category>
            <category><![CDATA[agile-modeling]]></category>
            <category><![CDATA[primary-app]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Thu, 07 Nov 2019 05:01:17 GMT</pubDate>
            <atom:updated>2019-11-07T05:01:17.456Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a quick update about what has been going on over the past month since our last release. We’ve also included a glimpse of where we are headed with new features in development.</p><p>Communication is the central theme of this update. Over the past month we’ve had lots of conversations. Thanks to all the users who took time to contact us in the last month. I am not sure what happened but we hit some communication inflexion point. The insights into how Primary users are modeling has been invaluable to us. It has also led to decisions and work on some new major product features.</p><p>Before we talk about the future, let’s go through the shopping list of updates:</p><h3>1. User Avatar</h3><p>We now have a user avatar that displays next to comments. By default it uses <a href="https://en.gravatar.com/">Gravatar</a>, so you may have your custom image there already.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/30/0*LgsXC3pPq8PZbtHo" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/0*u-hBZ-OVWzJG5yBK.png" /></figure><h3>2. Commenting updates</h3><p>There were many updates to the commenting system rolled out this month, so many I’m going to give them a bullet list:</p><ul><li># tags — you can create and filter by custom # tags. I am using #TODO as a standard way to keep track of things I need to change in the model.</li><li>Filter and Search — the Message Centre now includes a filter and search feature to find comments.</li><li>Release Comments — release comments are sandboxed so that working branch comments don’t appear to a viewer of a specific release. No need to air the dirty laundry during your model walk-through.</li><li>Better linking of comments to their parent Flows and Elements.</li></ul><h3>3. Show Interfaces in Share View</h3><p>You can now toggle the display of interfaces in the Flow overview in the Share View.</p><h3>4. Input behaviour standardisation</h3><p>There were a few annoying quirks and differences between the various input fields. We’ve done a lot of work to straighten these out and make them all consistent.</p><h3>New Directions</h3><p>We have two major projects under way, the first is a revamp of the pdf output. The current output is a little ‘dry’ to say the least. We are creating a framework to generate the pdf directly from the app, and following this we will be working on some nicer flow visualisations. Getting your stakeholders to appreciate your genius is so much easier with some pictures!</p><p>The second project involves a new meta level of User Journeys. This feature allows a high level pathway to be described. Activities on this pathway may or may not relate to Flows within the app being modeled. Accordingly the User Journey activities may be linked to one or more User Flows. Flows can be added as stubs in line to be developed later on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ac5a895de36" width="1" height="1" alt=""><hr><p><a href="https://medium.com/primary/august-updates-and-planned-new-features-9ac5a895de36">August Updates and Planned New Features</a> was originally published in <a href="https://medium.com/primary">primary</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[August Updates and Planned New Features]]></title>
            <link>https://medium.com/@james_primary/august-updates-and-planned-new-features-b41e35a51b83?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b41e35a51b83</guid>
            <category><![CDATA[user-flow]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[agile-documentation]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Wed, 06 Nov 2019 00:39:29 GMT</pubDate>
            <atom:updated>2019-11-06T00:39:29.481Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi ,</p><p>this is a quick update to keep you up with what has been going on over the past month since our last release. We’ve also included a glimpse of where we are headed with new features in development.</p><p>Communication is the central theme of this update. Over the past month we’ve had lots of conversations. Thanks to all the users who took time to contact us in the last month. I am not sure what happened but we hit some communication inflexion point. The insights into how Primary users are modeling has been invaluable to us. It has also led to decisions and work on some new major product features.</p><p>Before we talk about the future, let’s go through the shopping list of updates:</p><h3>1. User Avatar</h3><p>We now have a user avatar that displays next to comments. By default it uses <a href="https://en.gravatar.com/">Gravatar</a>, so you may have your custom image there already.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*C6fFbWgdaVSyjtQDX4QeuQ.png" /></figure><h3>2. Commenting updates</h3><p>There were many updates to the commenting system rolled out this month, so many I’m going to give them a bullet list:</p><ul><li># tags — you can create and filter by custom # tags. I am using #TODO as a standard way to keep track of things I need to change in the model.</li><li>Filter and Search — the Message Centre now includes a filter and search feature to find comments.</li><li>Release Comments — release comments are sandboxed so that working branch comments don’t appear to a viewer of a specific release. No need to air the dirty laundry during your model walk-through.</li><li>Better linking of comments to their parent Flows and Elements.</li></ul><h3>3. Show Interfaces in Share View</h3><p>You can now toggle the display of interfaces in the Flow overview in the Share View.</p><h3>4. Input behaviour standardisation</h3><p>There were a few annoying quirks and differences between the various input fields. We’ve done a lot of work to straighten these out and make them all consistent.</p><h3>New Directions</h3><p>We have two major projects under way, the first is a revamp of the pdf output. The current output is a little ‘dry’ to say the least. We are creating a framework to generate the pdf directly from the app, and following this we will be working on some nicer flow visualisations. Getting your stakeholders to appreciate your genius is so much easier with some pictures!</p><p>The second project involves a new meta level of User Journeys. This feature allows a high level pathway to be described. Activities on this pathway may or may not relate to Flows within the app being modeled. Accordingly the User Journey activities may be linked to one or more User Flows. Flows can be added as stubs in line to be developed later on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b41e35a51b83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[July Update]]></title>
            <link>https://medium.com/primary/july-update-560e45a9df12?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/560e45a9df12</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 02:00:52 GMT</pubDate>
            <atom:updated>2019-07-24T02:00:52.760Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been a few months since I sent a release summary. We have made multiple releases over the past three months with another large one going out this last week. There have been lots of housekeeping and minor functional improvements, and some bugs 🐞. Most of them are too detailed to list here, and some are too embarrassing, so we’ll stick to talking about features.</p><h3>Comments</h3><p>If you are working in a multi-discipline team, you need the various team members to be able to communicate effectively. This release sees the comments system come of age and really start to deliver on the promise. It has been updated with notification icons visible on Steps and Flows.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/0*DR_fAU2ugNZfrx6E.jpg" /></figure><p>​</p><p><em>Blue icons mean that there are new comments, grey means that they have been seen already.</em></p><p>Comments are now linked to the relevant Flow, Step or Element from the message center, and the message center icon also changes when there are new comments.</p><p>Team members now have configurable role badges to better identify who is saying what.</p><p>​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/0*0DaAD72cSA1ls9Bi.jpg" /></figure><p>​</p><p>Don’t forget that you can @ reference other team members in your comments and the mentioned team members will receive a notification.</p><h3>Version History</h3><p>Version history is now better organised, remember you can use the project Fork feature to roll-back you project to an earlier state, or copy it as a template.</p><p>As always we invite you to send in your suggestions for new features or reports of anything that’s a bit whack 🙃. Get in contact via the Intercom widget in-app, or send an email to hello@primary.app. Stay agile, people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=560e45a9df12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/primary/july-update-560e45a9df12">July Update</a> was originally published in <a href="https://medium.com/primary">primary</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[April Updates]]></title>
            <link>https://medium.com/@james_primary/april-updates-1f985730162b?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f985730162b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[tools-for-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Fri, 17 May 2019 00:29:42 GMT</pubDate>
            <atom:updated>2019-05-17T00:29:42.732Z</atom:updated>
            <content:encoded><![CDATA[<p>April’s updates are in the wild, we have a new introductory offer (but you have to earn it), and some methodological magic care of UX Collective.</p><h3>Goodbye to on-boarding</h3><p>We have targeted new users this month, so the on-boarding you probably endured when you signed-up has gone. Yay! 🍾.</p><p>We now have a less intrusive tip system with useful information about how to build a better model.</p><h3>Fork That</h3><p>For you committed modelers, we have the new ‘Fork at Change’ feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/0*YXgxHRt810Kfn4P0.png" /></figure><p>​You can now copy an existing project at a specific change number to a new project (Not for free accounts, sorry 🤷‍♂️). This allows you to either create a new model from the base of another model, or to roll-back a project to a specific point in time. Navigate to the Version History view under Project Settings.</p><h3>Free introductory month</h3><p>For those of you who are busy modelling with Primary, and are getting up near the flow limit, we’ve introduced a new introductory free month 🎁. No card details are required. You won’t need to worry about remembering to unsubscribe 📅, at the end of the trial you’ll be prompted to go Pro or downgrade back to a free account. We’ll email 📧 you with the offer when it is time.</p><h3>Agile Modelling article published</h3><p>Our good friends at the UX Collective have published a new article of ours about the process of Agile Modelling. We won’t repeat ourselves here, you can click the button below.</p><p>​<a href="https://app.intercom.io/#"><strong>Read all about it</strong></a>​</p><p>Get in contact via the Intercom widget in-app, or send an email to hello@primary.app. Stay agile, people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f985730162b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to use agile modelling to do more effective UX design]]></title>
            <link>https://uxdesign.cc/how-to-use-agile-modelling-to-do-more-effective-ux-design-f3939b0142e8?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3939b0142e8</guid>
            <category><![CDATA[application-development]]></category>
            <category><![CDATA[user-flow]]></category>
            <category><![CDATA[modeling]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Wed, 15 May 2019 00:18:24 GMT</pubDate>
            <atom:updated>2019-05-15T00:18:24.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJMkV5VWtaiTNvctLfWPTw.png" /></figure><p>So many tools, buzzwords and medium articles, so little time. My intention with this article, is to create an <strong>ah-ha moment.</strong> The detail can unfold later. I am talking about how User Flows and agile modelling fit into your design process.</p><p>You may have read Alex Handley’s <a href="https://uxdesign.cc/the-biggest-wtf-in-design-right-now-87139f367d66">article</a> which gives a good introduction to the <strong>“What”</strong> of User Flows. I’m going to put that in context of the<strong> “How” </strong>and <strong>“Why”</strong> of the app creation process.</p><p><strong>Contents</strong></p><ul><li><strong>What is agile modelling</strong></li><li><strong>Model first, UX second</strong></li><li><strong>How to run the process</strong></li></ul><p><strong>What is Agile modelling</strong></p><p><a href="http://www.agilemodeling.com/essays/introductionToAM.htm">Agile modelling</a> is the process of creating an easy-to-understand representation of how an app is going to both look and work. Its <strong>agility, comes from the process of iteration</strong>, and a willingness to throw away early versions and re-design based on new insights. To do this effectively you need a tool-set that helps keep track of your thinking, and allows easy communication to the entire product team.</p><p><strong>Model first, UX second</strong></p><p><a href="https://medium.muz.li/top-10-most-interesting-ux-design-case-studies-to-inspire-your-service-reinvention-in-2018-ea2309e4104b">Great UX interactions</a> can be hugely important, think of swipe-left/swipe-right. That one swipe interaction arguably shot <a href="https://tinder.com/">Tinder </a>into the big time. Having said that, the opportunities to create a game-changer on UX alone are few and far between. If the app you are designing relies on interactions alone for its success,<strong> I suggest you may not have a unique selling proposition</strong>. The starting point for an app design is a customer experience journey and business outcomes. UX design is informed by and aligned with the CX to achieve the business outcomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/0*CcP2zyqtjOP9s2R4.png" /></figure><p>My flavour of agile modelling employs <a href="https://uxdesign.cc/when-to-use-user-flows-guide-8b26ca9aa36a">User Flows</a> to map the processes that an App provides to support these higher level outcomes. The initial model of the app should be thought of as a straw-man. Depending on who is creating it, it will necessarily be canted in the direction of their experience. I think the best role to carry out this first cut is the <a href="https://www.mckinsey.com/industries/high-tech/our-insights/product-managers-for-the-digital-world"><strong>Product Manager</strong></a>. They have the customer in mind, and understand the business constraints and desired outcomes. Things will change when the model is socialised with the rest of the team. Clunky processes will be identified, technically infeasible features will be removed, <strong>overlooked opportunities will be identified</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/0*VbZhiMOlw6l2J52c.png" /></figure><p><strong>How to run the process</strong></p><p>If it all sounds good in theory, <em>you might be wondering ‘How do I do this?’</em> Just like a User Flow has some formality, socialisation of the model works best if you <strong>follow a specific process</strong>. This process is called a <strong>‘walk-through’</strong>. The walk-through is conceptually pretty simple, but there are some subtleties that, if unknown, can derail your session.</p><p>The walk-through requires <strong>the stakeholders to step through the user flows together</strong>. The author of the flows will typically lead the session, reading out the step text for each step of each flow, and reviewing any <a href="https://medium.com/sketch-app-sources/how-to-design-beyond-the-interface-b75f4b2b927a">attached elements</a> (<em>interfaces, business rules, data, and input forms</em>). It is important not to skip, but to go through all the flow detail in a measured way.</p><p>I know it sounds a bit dry, but there are two things I can guarantee during this process:</p><ol><li><strong>Obvious mistakes will be exposed </strong>on the first flow you review. Expect this will be the case but don’t let it hijack the process. Make a note of the change and carry on as if <strong>this is business as usual</strong>, because it is.</li><li>The other <strong>stakeholders will resist the process</strong> for the first one or two flows. They will want to skip ahead, try to give a blanket ok, or use some other device to escape. <strong>Keep them all engaged</strong>, because all of a sudden, the value will dawn on them. I’ve done this many, many times, and this ALWAYS happens. Once they engage, you will start to find the gold.</li></ol><p>By the end of the walk-through, your entire team will be able to discuss any part of the future software <strong>as if it has already been built</strong>. I’ve seen intense debates about how a particular feature should operate in a system that exists only as a model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/0*CtQZbVDya0mM96eX.png" /></figure><p>Flows can be modeled in a document, with cross references to your UX designs and a register for the other elements. Personally, I use <a href="https://www.primary.app/">Primary</a>, no surprises there, as it cuts down on the management overhead. Now you’ve built a model, and <strong>the entire team is in furious agreement</strong>.</p><p><em>How do we breathe life into your new monster?</em> If you look at your flows, you will no doubt have too many to complete in a single sprint. Select one or more, depending on the size, to form the first scope of work for your initial implementation. The flow format, with its supporting elements, will <strong>form an accurate picture for the dev team to work from</strong>. Having sat in on the walk-throughs the programmers can then use the flows as a visual cue and a reference for the more detailed information like form fields.</p><p>At the end of the sprint, any as-built changes can be fed back into the model. That way, it is ready to create the output for the next sprint. Flows can also be used as a script for user testing. Check each rule, form, interface and data element as you move through the flows.</p><p><strong>TLDR;</strong> Summarising all that, we could say:</p><ul><li>Model your app with User Flows.</li><li>Optimise the UX of those flows by iteration.</li><li>Get buy-in and optimise through repeated walk-through reviews.</li><li>Feed back any as-built changes to keep the model up to date.</li></ul><p>Stay agile, people!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3939b0142e8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-use-agile-modelling-to-do-more-effective-ux-design-f3939b0142e8">How to use agile modelling to do more effective UX design</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[March update]]></title>
            <link>https://medium.com/primary/march-update-431c38142402?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/431c38142402</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-model]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 05:17:42 GMT</pubDate>
            <atom:updated>2019-03-29T05:17:42.427Z</atom:updated>
            <content:encoded><![CDATA[<p>The team continue to knock over ‘small’ things that have have a big impact. Some have been on the list for a while, so it&#39;s great to get them out.</p><h3>The big bad Back Button</h3><p>You will have noticed that every now and then you’d click ‘Back’ in your browser, and if we are being honest, the UX sucked. No longer. Back will do just what you expect, it will take you back to previous screen, and where that isn’t even a thing, it will guess what you meant and take you there instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/0*b52rNeHqqptqD-xA.jpg" /></figure><h3>Translation for your Actions</h3><p>You can now overwrite the ‘Action verbs’ for Elements with your own versions. Principally this is to allow translation into languages other than English, but who knows? Check out the little ‘edit’ link in the dropdown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*xvgHasPPSFfB080d2I-4fQ.png" /></figure><h3>Thumbnails on the Interface Element page</h3><p>This one came as a direct request from a long-time user, and it made so much sense we pushed it up the list. For people using the Sketch import this change makes a lot of sense, as you can easily identify the Interface from its thumbnail and update the name in Primary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*3nS3vupG1hB7KE5FZroBbA.png" /></figure><h3>Commenting updates — Share projects, @ notifications</h3><p>Commenting now supports exchanging comments in ‘Shared with me’ projects. You can share your project with a client or consultant external to your team, and they will be able to @ you in comments, and see any comments relating to the shared project. In addition you will now receive emails when you are mentioned, or if its just too much yada yada, you can turn off notifications in the Communication Preferences section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*GKe1nCqsgOBC-IyxaT56ww.png" /></figure><p>We are queuing up the work for April, and there just might be some room in the schedule for an idea you have had. Two features in this last release are the result of user feedback, so please let us know if something is bugging you, or you have an idea so crazy it just might work.</p><p>Get in contact via the Intercom widget in-app, or send an email to hello@primary.app. Stay agile, people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=431c38142402" width="1" height="1" alt=""><hr><p><a href="https://medium.com/primary/march-update-431c38142402">March update</a> was originally published in <a href="https://medium.com/primary">primary</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In-line action edits and element status]]></title>
            <link>https://medium.com/primary/in-line-action-edits-and-element-status-5961204e01b9?source=rss-5bb90c3b7a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5961204e01b9</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[agile-documentation]]></category>
            <category><![CDATA[agile-modeling]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <dc:creator><![CDATA[James Billson]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 23:06:34 GMT</pubDate>
            <atom:updated>2019-03-04T23:06:34.160Z</atom:updated>
            <content:encoded><![CDATA[<h4>As summer draws to a close in the Southern hemisphere, the Primary team are putting down their BBQ tongs 🍖 and getting back to the keyboard.</h4><p>We’ve got some nice little features in this end-of-February release:</p><h3><strong>In-line action edits.</strong></h3><p>This is actually a bit of a cheat, as its an old feature that has come back due to popular demand. You can now edit the Step Action text in the Flow view without having to click through to the Step detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*ZkNmMs5RkCpd33aqK9oD0g.png" /></figure><p>This is really convenient when you are just spitballing your flows and getting the structure sorted out, as well as just being plain handy at other times.👍</p><h3><strong>Element Status.</strong></h3><p>Unlike teenagers, Elements now tell you if there’s something wrong. If Elements are not used or they are ‘stubs’ that contain no detail they are flagged on the Element list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*ZxET7I3AgJBWc85DvcEUZA.png" /></figure><p>This allows a quick glance to identify and remove redundant Elements, or to highlight Elements that need further definition work, like defining a rule, or adding fields to a form.</p><p>We’ve done a little housekeeping too ✨Hopefully you won’t see any of that, its all to do with status monitoring and the like.</p><p>Make sure you get in touch with us via email and/or intercom if you have even the tiniest question. We live for that stuff.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5961204e01b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/primary/in-line-action-edits-and-element-status-5961204e01b9">In-line action edits and element status</a> was originally published in <a href="https://medium.com/primary">primary</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>