<?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[Visibuild Product Team - Medium]]></title>
        <description><![CDATA[Powering construction through real-time data - Medium]]></description>
        <link>https://medium.com/visibuild?source=rss----33464ad90293---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Visibuild Product Team - Medium</title>
            <link>https://medium.com/visibuild?source=rss----33464ad90293---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 15:13:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/visibuild" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Is the handover file dead?]]></title>
            <link>https://medium.com/visibuild/is-the-handover-file-dead-e93284378ee2?source=rss----33464ad90293---4</link>
            <guid isPermaLink="false">https://medium.com/p/e93284378ee2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[claude-design]]></category>
            <dc:creator><![CDATA[Renee Phelan]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 22:26:06 GMT</pubDate>
            <atom:updated>2026-06-09T22:58:52.137Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FcZjBnFY9M7K_ZH-_nxSAA.png" /></figure><p>Maybe not dead. But in the last few months, it’s a step I’ve been able to skip completely without compromising on the quality of what we’re building.</p><p>For most of my career, designing something followed the same rough workflow. Low-fi journey maps to conceptualise an idea and get feedback. High-fi prototypes to bring it to life and test with customers. And finally, once you felt ready, the handover file: typically a big page in Figma with annotated specs, edge cases, and interaction notes that engineers could use as the source of truth when building.</p><p>At Visibuild, we’ve always worked in a collaborative and agile way with our engineers. But even so, there’s always been a need for the handover file to exist, for the specs to be written down. Lately though, it’s become clear that the process of creating it has actually been working against us. Slowing the conversation down, not opening it up.</p><p>Creating prototypes and handover files is a time-consuming process, so once you moved to documenting the solution for handover, the prototype would often get left behind. Every small update from then on got applied to the specs, not the prototype. The prototype stopped being the source of truth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjbXhpQ13fQPkOhDxMI0LA.png" /><figcaption>Once you start to document designs for handover, the live prototype gets left behind and is no longer used by the team</figcaption></figure><p>What we lost was the dynamic, realistic version of the solution. The thing people could touch and play with, replaced by a static, complex page of notes and arrows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Bc42LHd5PXI2RJ2IO1TwA.png" /><figcaption>Well intentioned “handover files” are cumbersome to create and maintain — and difficult to digest</figcaption></figure><p>Now I have a new process: prototyping with Claude Design, or directly on a branch from our codebase using Claude Code. I can build interactive high-fi prototypes fast enough that they replace both the polished Figma file and the handover doc. <strong>The prototype becomes the source of truth, and engineers build straight from it.</strong></p><p>More than just saving time, the quality of the prototypes I’m now creating is far better than before. Claude prototypes work like real, functional apps. They have interaction logic and mock data behind them, not just visual states. When testing, users can click anywhere, type anything in, and follow whatever natural pathway they want to take. Before, you’d wire up your prototype to work with a few chosen journeys, and if a user clicked somewhere they shouldn’t, you’d have to step in with guidance. That kind of interference shaped the feedback you could uncover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*nrF6pfgVyllc8yLW6sBkpA.gif" /><figcaption>Users can click wherever they like, type in whatever they like, they no longer need to follow a strict rigid workflow we’ve pre-prepared</figcaption></figure><h3>What I actually skip</h3><p>Not the problem solving. Not the critical thinking. Not the testing. Not the customer conversations or the internal conversations to get alignment.</p><p>I still spend most of my time in low-fi land in FigJam. Mapping journeys, breaking down the problem, collating feedback. But once I get to a point where I’m confident in the solution, I can now skip the mid-fis and Figma prototyping completely. Instead, I move from low-fi FigJam straight to high-fi Claude prototypes or code directly. Creating the prototype now takes a day, not a week. The middle step isn’t a bridge anymore, it’s a detour I don’t need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GhFGKqxX-mg0I05_tSNN6g.png" /><figcaption>Low-fi journey mapping and problem framing is where we spend most of our time — the important groundwork that allows us to speed through prototyping</figcaption></figure><p>When the prototype is the build target, the translation layer (the handover file) is redundant. Engineers look at the prototype, read the components, and fill in the gaps with judgement. The judgement was always going to be there. The spec was just slowing it down and creating a huge lift for designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*2gGlihZU4utl_JQK6HATlg.gif" /><figcaption>Interaction pattens that were previously difficult to prototype in Figma are easy, we now have more control in communicating how we want things to look and functional</figcaption></figure><p>Another benefit: updating the prototype when you get feedback takes minutes, not hours of going through designs, tweaking components, and making sure the prototype still works. If it’s easier to be adaptive to feedback, you’ll seek it out more readily.</p><p>A caveat though: the speed of creating a great prototype only happens if you’ve done the messy groundwork in shaping the solution and nailing down the user journeys first. Without that, you’ll just get something that looks nice but hasn’t really been thought through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IqJGQWs--tdgSoVyr8jQeA.png" /><figcaption>The part we see: visuals and prototypes are faster than ever, but the quality of those solutions depends on all the invisible work that you do before</figcaption></figure><h3>What’s harder</h3><p><strong>Pixel perfection is fuzzy now.</strong> The prototype gets you 90% of the way. The remaining 10%, like spacing, micro-interactions, and edge cases, falls back on engineers to interpret. And in many cases, we as designers are jumping into the code and making those final changes ourselves. We have the vision, and getting that last 10% of polish is now possible. That’s actually a positive change. It leaves more space for the team to use their best judgement instead of rigidly following a spec.</p><p><strong>The starting got cheaper. The finishing didn’t.</strong> Spinning up a new prototype or creating a PR from your codebase costs nothing now. It’s tempting to jump straight in and skip important steps, so we have to be really disciplined here. If we start too many things, we end up with a huge list of WIP to close out. Every new idea still creates work for the team to evaluate, plan around, ship, or kill.</p><h3>Rethinking the design system</h3><p>One unexpected consequence of all this: we’re starting to re-assess our design system.</p><p>When the prototype is the spec, the gap between “what the prototype looks like” and “what the production app looks like” becomes the new grey area. The closer we can pull those two together, the less interpretation engineers have to do, and the more confidence everyone has that what shipped matches what was designed.</p><p>So we’re looking at how to prototype directly from our real components. Pulling from Storybook, using the same tokens, the same primitives, the same patterns the production app uses. The dream is a prototype that isn’t a representation of the app, but built from the same materials as the app itself.</p><p>We’re not there yet. But it’s clearer now what “there” looks like.</p><h3>What hasn’t changed</h3><p>The work that matters most is still invisible. Customer conversations. Problem framing. Stakeholder alignment. Trade-offs. That work is messy and takes time. If anything, it matters more now. The visible work is so cheap to produce that the invisible work is what differentiates good design from bad.</p><p>So, do we still need the handover file?</p><p>For us at Visibuild, less and less. And that’s mostly a good thing. The artefacts we built our careers around weren’t sacred. They were workarounds for a constraint that no longer exists.</p><p>But it’s early. Every designer on our team is finding their own version of this. In six months, we’ll know more.</p><p>For now: one living prototype, all the way through.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e93284378ee2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visibuild/is-the-handover-file-dead-e93284378ee2">Is the handover file dead?</a> was originally published in <a href="https://medium.com/visibuild">Visibuild Product Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let users take the wheel: How customers course-corrected our latest feature]]></title>
            <link>https://medium.com/visibuild/let-users-take-the-wheel-how-customers-course-corrected-our-latest-feature-3f7d8b308499?source=rss----33464ad90293---4</link>
            <guid isPermaLink="false">https://medium.com/p/3f7d8b308499</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[construction-management]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[feature-engineering]]></category>
            <dc:creator><![CDATA[Dennis O'Keeffe]]></dc:creator>
            <pubDate>Fri, 25 Nov 2022 04:27:41 GMT</pubDate>
            <atom:updated>2022-11-25T05:28:50.093Z</atom:updated>
            <content:encoded><![CDATA[<h3>A case study on preemptively solving customer problems through their behaviour</h3><p>A feature that recently made its way onto our product roadmap at Visibuild was the capability to <a href="https://visibuild.canny.io/changelog/export-multiple-pdfs-at-once">export multiple PDFs for Visis through any project location page</a>, aptly named Bulk PDF Exports. Given our previous updates that enabled users the ability to <a href="https://visibuild.canny.io/changelog/filter-qa-data-on-your-location-pages">filter Visis</a> based on a chosen location, the next logical step was to empower users to export that data.</p><blockquote>Note: A Visi is the broad term we use to describe Tasks, Inspections or Issues within the product”</blockquote><p>Working at a startup poses interesting challenges for those working in product development, and kicking off a new project requires our team to come together and realign on the feature and its place on our priority list, particularly given the small size of our product team!</p><p>Entering the market quickly and bringing your product up to competitive feature parity and building out the “why we’re different” moat requires ruthless prioritisation as well as some creative, short feature-release timelines with a willingness to roll-forward or pivot at short notice.</p><blockquote>Entering the market quickly and bringing your product up to competitive feature parity and building out the “why we’re different” moat requires ruthless prioritisation.</blockquote><p>For each product feature we kick-off, we as a team make some best-effort estimations around a few key trade-offs:</p><ul><li>Time-to-market.</li><li>Feature validation.</li><li>Feedback cycles from the end-user.</li></ul><p>There is always a fine balance between feature release and engineering. Underbake the feature and you <em>risk</em> <em>breaching trust between your customers and your new feature</em>. Spend too long in the oven and your customers may already have found alternatives that satisfied their immediate needs.</p><p>At Visibuild, we are working closely with our customers and remain transparent so that our finger is on the pulse and we can prioritise what needs to be done as effectively as possible. Once these decisions have been made, the internal team works together to put together the vision of the feature and work backwards on slicing up the end-goal into actionable pieces that help to bring value to the customer as soon as possible. Part of that process includes our efforts to predict things that could go wrong, how we can preemptively track those outcomes and also how we can roll forward in the case that the issue is considered a “deal breaker” on the promise that the feature makes.</p><p>One feature that I recently built out was the ability for customers to <strong>bulk export PDFs</strong> of our customers “Visis” (a universal umbrella term that covers the project’s inspections, issues, tasks and non-conformance reports).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-apaHIpFzyG2CgXK_pgWg.png" /><figcaption>Our feature release that enabled users to select multiple Visis for bulk PDF export.</figcaption></figure><p>This feature was heavily requested, and we wanted to slice up the end-result into iterations that enabled us to get the feature out to users quicker.</p><p>We sliced up the iterations for this feature into two pieces:</p><ol><li>The first iteration would introduce the customer-facing UI on the web application and utilise the backend flow we already had for emailing out PDF exports for a single Visi as an email attachment.</li><li>The second iteration would focus on replacing the emailed zip files with the PDFs, storing those zip files remotely and replacing the email attachment with a link to the downloads.</li></ol><p>The problem that we identified with the first flow is the limitation of email attachments. There is an attachment size limit for the emails that we know we would eventually hit as project data becomes larger in size and generating exports for those Visis becomes more complex in both size and nature.</p><p>As users begin to use our feature more, the likelihood of running into this issue increased significantly. Some of the factors that went into this (that we could identify) would include the number of attachments for a Visi, as well as the amount of Visis requested for the export.</p><p>Given this <strong><em>known assumption</em></strong> when defining our first iteration, we capped the bulk exports to have a maximum of fifty Visis that could be requested for export at one time. This cap was not designed to put a cap on our customers, but we knew that measuring this and enforcing the limit would give us the opportunity to release the feature earlier and collect usage statistics to help us make an informed decision on the second iteration to move to the download links. The cap would not prevent the possibility of a failure due to the attachment size being large, but given the arbitrary nature of the PDF attachment size, we figured that it would certainly help mitigate the risk of too many failing exports.</p><p>The decision of the cap afforded our product team some breathing space which in turn gave us the chance to spike out the solution for the second iteration of replacing the zipped PDFs while getting value out to customers faster.</p><h3>Statistics from the early adoption</h3><p>At Visibuild, our aim is to let customer feedback and tracked actions drive our product direction.</p><p>Given the agreed upon limitations of the email attachment for the first iteration, tracking was added in to view which projects were using the new feature, how many Visis they were attempting to export as part of the request and a way to capture the errors if exports became too large for email attachments.</p><p>As it turns out, <em>even within the first week</em>, bulk exports were used to export in larger batches than initially hypothesised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ikfVceXDwfAda3dyBQLCAw.png" /><figcaption>Statistics on usage within the first week of release.</figcaption></figure><p>The above graph displays the number of Visis requested for PDF generation per request. Within the first week, there were some early signs that users were requiring the full extent of the new feature’s capped export limit.</p><blockquote>Within the first week, there were some early signs that users were requiring the full extent of the new feature’s capped export limit.</blockquote><p>One request even managed to run into the <em>exact</em> scenario that we wanted to avoid: failure to send an email because of the ZIP file attachment hitting the size limit.</p><p>Our support team worked on ensuring that the failed export was supplied to the user who made the request, but we also identified and understood prior to release that issues such as this would be costly for our support team if they continued to occur, <em>particularly as feature adoption would only increase exponentially</em>.</p><p>Ultimately, we only had one failure from the first one hundred requests. Our decision to release the first iteration still worked in our favour. <strong>We had delivered value to customers for 99% of requests</strong>. That being said, this early usage, direct customer feedback and the first incident were all references that informed our decision to bring forward the next iteration of using download links over attachments up the priority list.</p><blockquote>Early usage, direct customer feedback and the first incident were all references that informed our decision to bring forward the next iteration.</blockquote><h3>Rolling forward into the second iteration</h3><p>At the end of first iteration, the workflow for exporting multiple Visis could be simplified into the following state chart:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2LafbtAt435USH403KOp8A.png" /><figcaption>A simplified state chart that guided how the workflow of bulk exports work for our first iteration.</figcaption></figure><p>The agreed upon technical solution to take this forward to the next iteration meant that the following changes had to be made:</p><ol><li>Introduce a way to track the <strong>state</strong> of a bulk export job i.e. <em>is the job pending, in progress, fulfilled or rejected?</em></li><li>Ensure notifications occur for both successful and unsuccessful jobs to keep the end-user informed.</li><li>Build a secure mechanism to store and access exported ZIP files.</li></ol><p>The next iteration would update our workflow could then be simplified to the following state chart:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xqYfCoqpm4Xn_amtjSlnAw.png" /><figcaption>A simplified state chart that guided how the workflow of bulk exports work for our second iteration.</figcaption></figure><p>This solution meant that we would resolve the issue around attachment sizes, as well as be more proactive on letting customers know if there was an issue that occurred during the bulk export process.</p><h3>The final solution</h3><p>After working with the rest of the product team to define the next iteration of the user experience, we implemented an updated set of email flows to keep the user informed. We also defined, implemented and tracked a set of states that the job could be in and how we could best reflect that through the user interface on our export download page to ensure that any further issues would be front-of-mind and addressed by our product team.</p><p>The new flow would start with the user requesting a new export and the success notification positioning the time frame for the export to give the user a better idea of how long exports may take.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z1CUsB_OgvhXeERfcS0a9w.png" /><figcaption>The new notification would position a better time frame for end-users.</figcaption></figure><p>Once the export had completed successfully and was ready to download, an updated email would now provide the link as opposed to an attachment. This addresses our issue on the attachment sizing problem that we ran into. The link would direct a user to our new <strong>exports download page</strong> which would give them information on the current state of the export and a link to download the export in the event that it was ready (and not expired).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nt7dGKp3ww2Fw-kBM7WY_Q.png" /><figcaption>The first look of our updated email sent to users when an export had been fulfilled.</figcaption></figure><p>Clicking the download link would provide the download page for the user to download the PDF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CpEadbbqtbmd8Adc1Q6HKQ.png" /><figcaption>The new export download page provided a link to download the asset, as well as positioning on how long the link would remain active for.</figcaption></figure><p>Alongside the download link, we include the time until the link would expire. The decision was made to ensure that we set the link to “expired” after 14 days given that exported PDFs generally move into a stale state soon after the export.</p><p>This new approach with the expiry built-in enabled us to think forward on the costs of hosting these PDF export requests as remote ZIP files. This helped us to budget the new feature at scale, with our backend set to automatically remove these stale ZIP files and save on costs for data that would no longer be used.</p><blockquote>This new approach with the expiry built-in enabled us to think forward on the costs of hosting these PDF export requests as remote ZIP files. This helped us to budget the new feature at scale.</blockquote><p>In the case of a failure, we also had an email set to inform the user that an issue occurred to resolve the issue of “silent” failures causing customers to contact us about issues. This enabled us to be proactively transparent with a customer, as well as giving them the option to contact us for further information if desired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rw0ncAsMxxgLmk5QFhs9yA.png" /></figure><p>The final piece of the puzzle was to keep the user interface for our export download page informative with the different job states that it could be in. For us, that meant ensuring the user was informed if a job was queued, in progress, failed, expired or in an unexpected error state.</p><p>Some of those states were represented in the user interface as the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oUwse5bin1Ici5i-E7mJWw.png" /><figcaption>The user interface when a failure occurred.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLukRwflXyWnk74e2zJd3A.png" /><figcaption>The user interface when an exported was currently in progress.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SzHTBs6Yhsy8oFUyiQVusw.png" /><figcaption>The user interface when an export had been queued by the job was still yet to begin processing.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXjvR3ehWl4ZgXqVF9wWAQ.png" /><figcaption>The user interface when the result was in an unknown state.</figcaption></figure><p>Thanks to the updated user interface, we could ensure that users were empowered to check the progress of any given export request and understand where that request sits at any stage of the job lifecycle.</p><p>The updated lifecycle of the our new flow over time could be simplified and summarised as the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2tk5PIK5Lr-gB4IKD2AjmQ.png" /><figcaption>The Visi PDF export lifecycle for single PDF export requests and bulk PDF export requests.</figcaption></figure><p>This flow gives an overview of the lifecycle for all our PDF exports as they occur for single PDF exports, bulk PDF exports (more than one PDF export in a request) and the failure flow for both the single and bulk PDF exports as those flows run over time.</p><h3>Recount, outcome and results</h3><p>At the time of writing, our iteration on the feature has been shipped and we have kept a close watch on the outcome and results.</p><p>To recount, we began with the first iteration that focused on getting the capability out to customers while keeping the end in mind in order to understand the next steps while keeping the roadmap fluid enough to action those steps at the appropriate time. After considering usage analytics and customer feedback, we promoted the implementation of our second iteration up the roadmap.</p><p>This second iteration had an end-goal to <strong>solve and workaround the issue of attachment sizes and work towards unlocking the hard Visi export limit that we have set for customers</strong>. We did this by migrating our previous approach of directly attaching exported ZIP files to emails as attachments and instead opted to make use of an interim storage solution and download links.</p><p>Thanks to this latest iteration, we have <strong>successfully mitigated these issues</strong> and no more requests have come in around failed exports due to the attachment size.</p><p>In the time since the release of this new iteration, adoption of the feature has <strong>increased over 370%</strong>. Our decision to move up the iteration on the roadmap has likely prevented a few headaches and tough conversations with our customers.</p><p>This project showed the collaborative mentality we share at the company. By keeping the end in mind, we preemptively acknowledge potential pitfalls in early iterations, as well as re-enforce our company value to pivot and address any high-risk and problematic issues if they occur earlier than anticipated.</p><blockquote>By keeping the end in mind, we preemptively acknowledge potential pitfalls in early iterations, as well as re-enforce our company value to pivot and address any high-risk and problematic issues if they occur earlier than anticipated.</blockquote><p>The two iterations of the bulk PDF export feature that were covered in this recount demonstrate the importance of shipping value early and making decisions based on customer usage.</p><p>Running into the issue of users wanting to make the most of a feature is a good problem to have. As is often said in our team offices, “Ship to learn.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f7d8b308499" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visibuild/let-users-take-the-wheel-how-customers-course-corrected-our-latest-feature-3f7d8b308499">Let users take the wheel: How customers course-corrected our latest feature</a> was originally published in <a href="https://medium.com/visibuild">Visibuild Product Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup collaboration for speed]]></title>
            <link>https://medium.com/visibuild/startup-collaboration-for-speed-5df23461aecc?source=rss----33464ad90293---4</link>
            <guid isPermaLink="false">https://medium.com/p/5df23461aecc</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[async]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Renee Phelan]]></dc:creator>
            <pubDate>Thu, 25 Aug 2022 05:19:35 GMT</pubDate>
            <atom:updated>2022-08-25T05:19:55.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lUn2tub9CucF8UM5Hvb3ug.png" /></figure><p>In a startup speed is everything. Your ability to make quick decisions and adjust based on user feedback is crucial to moving faster than your competition and building a successful company.</p><p>Many startups today like ours <a href="http://visibuild.com.au/">Visibuild</a> are distributed, our team is based in Melbourne and Brisbane and we work in a hybrid model mixing office time with the flexibility to work from home.</p><p>We started Visibuild in 2021 during one of the many Melbourne lockdowns. This turned out to be a brilliant time to start a company as it meant we could take the learnings from how to work well remotely and bake that into our culture from day one. Taking the good and leaving the bad practices behind.</p><p>Here’s our approach to collaboration for speed at Visibuild.</p><h3>1. Create an async-first collaboration culture from day one</h3><p>The only way to move quickly with a distributed company is to be able to work together to solve problems and make decisions without relying on being in the same room or even on the same video call.</p><p>If you need to get everyone on a call or in a meeting just to move a project forward everything will happen too slowly. This is an old-school mindset that some companies struggle to move away from even with the introduction of remote work and video calls.</p><p>To move quickly without losing collaboration, default to async-first rather than a synchronous meeting-first culture in your team.</p><p>Empower your team to take control of their time and not feel as though they need to respond to messages immediately if it means shattering their focus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*8GP-nbh5R8pJOq1Tv0V2HA.png" /></figure><h3>2. Get good at communicating ideas in writing</h3><p>The key to great async collaboration is having everyone on your team able to communicate ideas in writing.</p><p>When you have to write your ideas out rather than just rambling on in a meeting it forces you to think more deeply and get clear on what it is you’re trying to say.</p><p>It also makes it easier for everyone to understand and give feedback. Especially for those who might not feel confident to speak up in a large group with many strong voices.</p><p>Whether it’s a customer problem (how to speed up onboarding) or an internal business problem (how to improve our product analytics), at Visibuild we always start by writing out a definition of the problem in what we call a “problem doc”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*kXRyY26mL-es8tZXQch4Bw.png" /><figcaption>The Visibuild Problem Doc template</figcaption></figure><p>Written in notion problem docs are then shared and the feedback process begins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*kGTrCo2iXH3jDTF3xa3oFQ.png" /><figcaption>Always start by writing out your understanding of a problem</figcaption></figure><p>If there are aspects to the problem we haven’t considered these are quickly brought up by the team, bolstering our problem understanding and leading to better quality solutions.</p><h3>3. When work is shared async make time to read it and provide feedback</h3><p>Async collaboration only works if everyone reads the work and takes the time to provide thoughtful comments or ask questions. Work is shared constantly in our team and that doesn’t mean you must stop what you’re doing right away but it does mean baking in time to provide feedback in a timely manner so that things move forward.</p><p>At Visibuild we encourage everyone to block out time in their calendars to review shared work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/181/1*fm-iYnEeIMdKBnFV0jIupw.png" /></figure><p>When you give your team the agency to run their own schedule rather than forcing them into a meeting to listen to your idea and provide feedback, everyone continues to move quickly without slowly down the broader team.</p><h3>4. Thoughtfully design your team’s meeting schedule</h3><p>Recurring meetings are like product features, it’s much easier to add them than it is to take them away.</p><p>If you run into an issue where lines of communication broke down or collaboration didn’t happen effectively resist the urge to reactively create a new meeting in the calendar to ensure the same thing doesn’t happen again.</p><p>Instead think about how you can adjust your async collaboration approach first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*hJbz1vr61O1rB2JgpOi-GQ.png" /></figure><p>Slowly-by-slowly meetings can add up and you and you’re team and left with less and less time to do deep work. Less time to work asynchronously.</p><p>At Visibuild we’ve designed our team meetings to ensure our distributed company remains connected, provide space for healthy debate and to share context. We respect the time of our employees and make sure that every meeting we add has a purpose and if needs to be on the calendar.</p><p>We also periodically review our meetings and make sure they still make sense.</p><p>To move quickly you need to ensure that everyone in your team has enough time to do their best work. Establishing an async-first collaboration culture will allow you to ensure you can foster healthy collaboration and keep your team moving forward without burning time on meetings.</p><p>We’ve been lucky to establish this culture from day one at Visibuild its equally possible in an established company, it simply requires a mindset shift and a change in behaviour.</p><p>Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5df23461aecc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visibuild/startup-collaboration-for-speed-5df23461aecc">Startup collaboration for speed</a> was originally published in <a href="https://medium.com/visibuild">Visibuild Product Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gathering user insights out on-site ]]></title>
            <link>https://medium.com/visibuild/gathering-user-insights-out-on-site-1120e7fdc80b?source=rss----33464ad90293---4</link>
            <guid isPermaLink="false">https://medium.com/p/1120e7fdc80b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[contextual-inquiry]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Callista Low]]></dc:creator>
            <pubDate>Tue, 16 Aug 2022 05:45:00 GMT</pubDate>
            <atom:updated>2022-08-16T05:47:42.749Z</atom:updated>
            <content:encoded><![CDATA[<p>Contextual inquiry is more than just a normal user interview. In the pursuit of trying to wrap your head around what users are hoping to accomplish and digging into the problems they face, asking users well thought questions in the place where they would use the product provides a much richer and holistic set of research data.</p><p>Context matters. The key value driven out by <strong>context</strong>ual inquiry is the <strong>context</strong> it provides. The products we design should take into account the time, place, and setting in which they are being used. As <a href="https://uxdesign.cc/contextual-inquiry-a-primer-14e2e0696fb9">Thornton</a> puts it, the combination of ethnographic work and user interviewing in this research method allows gaps to be filled in observations that would otherwise be overlooked.</p><p>Imagine having to design an app for a restaurant ordering system, sitting down in an actual restaurant and conducting an interview with users there would expose key user behaviour such as where they would expect to find the menu, how often they would pick up one, what they’re looking for and how to optimise the process for an online version. Users would also be able to more easily point out elements in the restaurant itself which would inform better insights for the designers creating the app.</p><p>While user interviews have been a fundamental research method for us at Visibuild, the act of reaching out to users and meeting them in the place where they are working not only allows us to observe the surroundings and the constraints that come with it but also helps our users recall important pieces of information of the tasks they carry out day-to-day.</p><h3>The stories and learnings from contextual inquiry sessions at Visibuild</h3><h4>First-times in the first week</h4><p>It was my first week at Visibuild. With my hard hat, fluorescent hi vis, and chunky construction boots strapped on, I was ready to head off to site for an in-person walkthrough of how buildings are built. My team and I were hoisted up to the 60th floor to take a tour around the site and to ask all the questions we had to wrap our brains around the wonderful and mysterious world of construction. It was an opportunity to delve into what our users get up to in their day-to-day, the frustrations they face, and the considerations we, as builders of the product need to think critically about. Down in the basements, I took a glance at my phone and realised how the internet connection was weak. It made sense how Visibuild has an offline mode to support this occurrence and not hinder our users’ workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hsJFyKNhA6zyzCQ6xbzdpw.png" /><figcaption>Riding a construction elevator for the first time.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6qrnWkRm45fe5WZ5YrhviA.png" /><figcaption>The Visibuild crew on the 60th floor of a construction project</figcaption></figure><h4><strong>Breaking new ground with unsolved problems</strong></h4><p>Currently, the way this client was approaching defects was by marking them down with coloured dots and then having the respective subcontractors come in to fix the issues. Once it was completed, the stickers would be thrown to the floor and cleaned up later on. This observation led to a realisation that there is a massive opportunity to break into. Problems such as the lack of accountability and awareness of the defect process were problems that our product can easily help combat. If we had not gone out on site, our visions and the future of the product will only be limited to what we know and we would have completely missed out on the chance to break into a massive opportunity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPheqjjCNyezV75vGZG8Yg.png" /><figcaption>Defect stickers placed around the unfinished kitchen on a construction site</figcaption></figure><h4><strong>(Most) users actually really enjoy being a part of the design process</strong></h4><p>It wasn’t long until I was given the opportunity to interview our users out on site to get further context into the problem I was working on. Given that I had little to no understanding of why the problem was a nuisance to their workflows or whether it was even a problem at all, it was the perfect situation to visit our beloved customers who had already been using Visibuild for some time.</p><p>Despite their jam packed 7am-10pm schedules, almost all the users interviewed lit up when they were able to test out the prototypes for our new and very much still a work-in-progress design. Applications like Figma, let alone the whole concept of rapid prototyping are completely new to them but they are almost always happy to share their thoughts when testing the designs.</p><p>Tailoring the problem to the specific scenarios they face not only sets the context behind the problem, but also gives them the space to share more about how it specifically impacts them.</p><blockquote><em>“Is this what you guys do? This stuff is f*****g cool!!“</em></blockquote><p><em>A user quote that’s in the Visibuild’s hall of memorable quotes</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e2KzI9294z-ElOkypsQJwA.jpeg" /><figcaption>A user testing session conducted in a construction office.</figcaption></figure><h3>A few tip-bits to take away</h3><h4>Get the most out of each site visit</h4><p>Let your users speak and listen to them attentively. As eager as you may be to show the designs you’ve been working on, this is an opportunity for you to listen to their struggles, the lows, the highs that they’re experiencing with your product. Often time, you’ll go back with so much more than you expected to get out of the session. There have been plenty of times where I intend to test one thing but then go back with a list of other feedback. While this may not be the intended route of the conversation, just listening to them talk about their ideas and problems drive out so many more important insights.</p><h4>Build relationships with your users</h4><p>User feedback is one of the most treasured resource a designer can have. They are essentially doing the company a huge favour and the least we can do is thank them and update them on the progress of where the project is heading. Even if they give you questionable design suggestions, smile, thank them, and always ask them why!</p><h4>Bring a buddy along!</h4><p>Take this opportunity to bring along someone outside of the design team! Exposing parts of the design process to other members of the team will help you, as a designer, to think critically about other perspectives. They are also incredibly helpful in writing notes, bouncing ideas off, pre-interview prep, and filling in the gaps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1120e7fdc80b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visibuild/gathering-user-insights-out-on-site-1120e7fdc80b">Gathering user insights out on-site 🔍🏗</a> was originally published in <a href="https://medium.com/visibuild">Visibuild Product Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why startups are career accelerators]]></title>
            <link>https://medium.com/visibuild/why-startups-are-career-accelerators-1da90f7b11d?source=rss----33464ad90293---4</link>
            <guid isPermaLink="false">https://medium.com/p/1da90f7b11d</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dave Allie]]></dc:creator>
            <pubDate>Tue, 26 Jul 2022 03:22:37 GMT</pubDate>
            <atom:updated>2022-07-26T03:22:37.248Z</atom:updated>
            <content:encoded><![CDATA[<p>Startups are fast-moving versions of their (much) older relatives — big corporates (or as our CPO Shaun likes to say, “hella corps”). Working at a startup and getting your hands dirty with new tools, directly impacting the success of the business, and exposing yourself to other areas of a business is a surefire way to accelerate your hard skills, your understanding of the big picture, and your career.</p><p>Thinking about potentially joining a startup? Read on. Absolutely convinced that big-corps are the way and not interested in startups? Read on and let me convince you otherwise.</p><h3>Gain exposure to new tech</h3><p>Startups are not anchored to tooling, language, or approach requirements, and encourage thinking outside the box where product differentiators are involved. Moving fast and freely is in their best interest, so focusing on a customer problem and the technical approach to solve it is often more important than making sure everyone is using the exact same outdated libraries.</p><p>Startups additionally allow you to build the critical context of when to use a tool or an approach, not just what that tool is, through debate, experimentation, or exposure. This experience and knowledge will allow you to take your learnings between industries and companies, creating clean system design, correct tooling choices, and knowing where to start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9XmM2JIpfbv7gKJ-YiKcRg.png" /><figcaption>Shaun presenting an idea for Keanu Reeves style Matrix view</figcaption></figure><p>Larger companies focus on homogeneity, forming an extremely well-trodden path upon which a set of well-known approved tools are used. They discourage (or even prevent) the ability to stray from that path. While it is possible to gain new exposure by hopping between teams periodically, this comes at a cost in the form of abandoning your team and starting over, or alienating others to the point of no mutual trust. Even within this homogeneity, big companies have a build-up of legacy baggage and complexity, drastically reducing their ability to move freely. Building a new small service within a massive network of outdated, incompatible, or incomplete micro-services isn’t fast or free. Don’t believe me? Watch this <a href="https://www.youtube.com/watch?v=y8OnoxKotPQ">too real skit</a>.</p><h3>Be heard, make your mark</h3><p>Startups encourage everyone to promote important and impactful problems for customers. At Visibuild, we use a combination of weekly WIP (work in progress) chats and Problem Docs (more on Problem Docs in a future blog post!) to help us communicate the root of the customer problem, why it’s important, and some potential ways to address it. These problems and solutions are synthesised from talking with customers, demoing prototypes, and internally iterating on ideas. From the point of a problem doc, building out and delivering the solution back to customers closes the loop from ideation to delivery. Being involved in helping define what’s important to the product and company both improves your critical thinking when it comes to product direction and is a whole lot more fun than just churning through tickets day after day.</p><p>Startups breed a culture of experimentation and ideation through the use of hack days, innovation sessions, or <a href="https://www.thesprintbook.com/the-design-sprint">design sprints</a>. These sessions focus on pushing boundaries by exploring new ways to approach and solve problems and are a core mechanism for product and personal growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hVizirnYbrTLA2O9" /><figcaption>Visibuild team design sprint for a redesigned home page — <a href="https://medium.com/visibuild/what-makes-good-products-great-make-things-personal-72a8fb7ad8ac">see Renee’s thoughts on home page personalisation</a>.</figcaption></figure><p>Getting a hand into the planning process and getting your ideas executed at big tech companies is nigh impossible. 2-pagers, 6-pagers, PR/FAQs, impact estimation, effort planning, review meetings, and cross-team alignment, all to get to the point of your idea being deprioritised for the upcoming 12 months of planned work. Better luck next time! Profit margins, long-distance planning, and big egos all conspire to make it punishing to see your ideas out in the world. Experimentation at big corporates is also tough. Generally, managers are not incentivised to experiment. They commit their teams to large potions of work in advance and work through that backlog over the year, typically without built-in slack for much else. At these big companies where everything is decided by financial impact, experimentation (which is difficult to quantify) is routinely undervalued and deprioritised.</p><h3>Understand how the sausage gets made</h3><p>In a startup you work extremely close with customers, and the barriers that are usually in the way are removed. You don’t need to ask anyone’s permission or fill in any forms to talk to your users. There is a massive difference between talking to customers directly to understand their problems, and hearing that same information second or third-hand.</p><p>Drawing your own conclusions from customers, instead of blindly following one person’s opinion is what makes a diverse and complete product. Following that customer discussion through product ideation to completion and taking part in the entire journey is something uniquely startup. Peeling back the layers of the business, and understanding how each part functions will help you communicate and work more closely with those areas in your startups (or other businesses) in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dc2vvhNQBRDnH9_t2pc6cA.jpeg" /><figcaption>Getting out to site to talk to customers</figcaption></figure><p>Understanding customers in large companies is like playing a game of Telephone, by the time the feedback gets to you, it has been reshaped by a bunch of people, twisting the original intent. Direct access to customers is often impossible. Beyond that, you’re discouraged from straying too far from your prescribed path, you’re either hired as a specialist or shaped into one. Keeping a foot in multiple camps, or exploring the process within the rest of the business is not typically possible.</p><p>Feeling stagnant, or think that the issues with hella corps mentioned hit a little too close to home? Then maybe it’s time for a change of pace, maybe it’s time to join a startup.</p><p>Thinking about stepping on the gas and accelerating your career? <a href="https://www.linkedin.com/company/visibuild-pty-ltd/jobs">Visibuild is hiring</a>! Feel free to visit our LinkedIn jobs, or to reach out to me directly!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1da90f7b11d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visibuild/why-startups-are-career-accelerators-1da90f7b11d">Why startups are career accelerators</a> was originally published in <a href="https://medium.com/visibuild">Visibuild Product Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes good products great? Make things personal.]]></title>
            <link>https://medium.com/visibuild/what-makes-good-products-great-make-things-personal-72a8fb7ad8ac?source=rss----33464ad90293---4</link>
            <guid isPermaLink="false">https://medium.com/p/72a8fb7ad8ac</guid>
            <category><![CDATA[personalisation]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Renee Phelan]]></dc:creator>
            <pubDate>Mon, 11 Jul 2022 23:09:01 GMT</pubDate>
            <atom:updated>2022-07-15T02:39:37.286Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever walked in to your favourite cafe and been warmly welcomed by the barista who knows your name and your order?</p><p>It’s a really nice experience and it feels personal. Like you have a connection with that person rather than it feeling just like a transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RoySh-n6ZjQvFFCMO7iRcA.jpeg" /></figure><p>When we’re using digital products we crave these same personal interactions. We want products to understand us and what we’re trying to achieve and then make those things easy.</p><p>This happens with product personalisation, an extra layer of UX design that can take a good product and make it exceptional.</p><p>In this post I’ll outline some great and not so great examples of what this looks like along with how you can get started regardless of whether your designing a B2B SaaS tool, a consumer app or anything in between.</p><h3>Examples — The good</h3><p>It’s no surprise that the most loved products on our phones are doing a fantastic job at personalisation.</p><h3>Spotify — Uniquely yours</h3><p>When you open Spotify, you want the right music to suit your current mood. But moods change and what we feel like listening to on a workday vs a Saturday night is very different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/0*_I9ttuMgP4hzyyBN" /><figcaption>Spotify’s home page suggests curated playlists to suit the day of the week and time.</figcaption></figure><p>Spotify cleverly use day of the week, time and location to present recommendations that suit the moment: focus music for work on a weekday and bangers on the weekend.</p><p>Spotify’s <em>Made for you</em> playlists tailored to our listening habits have become so good that we literally don’t need to make our own playlists anymore, Spotify does a better job.</p><h3>Google — Take me home</h3><p>Google is a master at using time and location to adapt based on whats going on in our lives outside the app. Google knows whether we’re at work or home and will adapt with different traffic and transport suggestions to get us where we want to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*aTuNS5_NTJKhfqyu5sGVAA.png" /><figcaption>Google recognises when I’m home vs at work and adapts travel suggestions to suit.</figcaption></figure><h3>Flo — your friendly assistant</h3><p>Flo is a brilliantly designed cycle tracking app for women that offers incredibly deep personalisation.</p><p>Women enter their personal goals (track cycle, fall pregnant), cycle dates and daily symptoms and then Flo provides predictions based on exactly what to expect each day.</p><p>Flo deepens their personalisation by delivering these insights via Flo-Assistant, a friendly chat bot that actually feels real.</p><p>The entire product feels personal, it draws you back each day and makes you feel like your engaging with a real personal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*jRGEo7fUf4sztxF81_d33Q.gif" /><figcaption>Flo Assistant delivers helpful guidance in a conversational chatbot experience.</figcaption></figure><h3>Examples — The not so good</h3><p>For personalisation to work it needs to feel natural and be useful. Here are a couple of examples that showcase that not all personalisation enhances the experience.</p><h3>ClassPass — a confused home page</h3><p>ClassPass is a great offering and although they do have some personalisation, they haven’t invested in the areas that really matter: helping their users find, book and attend classes easily.</p><p>The “For You” page doesn’t help me quickly do the things that matter and instead is really just a promotional space that I find myself navigating away from.</p><p>This could be the perfect location to bake in meaningful personalisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*EZy8IfY0DzG_J36eIccPgg.png" /><figcaption>The ClassPass home page fails to help users prepare or book classes easily and instead features promotions and a social feed.</figcaption></figure><p>ClassPass know the types of classes I like, my existing schedule and location. They could use this information to intuit what I need to do each time I open the app.</p><p>For example when I have an empty schedule this is when they should encourage me to book classes near me. But when I open the app ahead of an upcoming class, it should be easy to check the time and details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/0*rMQ921Ijq71j5ryw" /><figcaption>How ClassPass could personalise their home page based on their user’s situation.</figcaption></figure><h3>Commbank — For you, for who?</h3><p>Commbank is a well designed app, managing money is intuitive, but this is where the value proposition and personalisation stops.</p><p>Although there is a page in the app titled “For you” this feels like just a way to promote different products rather than actually things <em>for</em> <em>me</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*VGeb0mh9A69DzptNNLHCZw.png" /></figure><p>We all have different financial goals (budgeting for a holiday, increasing shares etc.) Commbank could identify what these are and then deliver a personalised product experience that helps users achieve them.</p><p>This is the approach smaller competitors like <a href="https://up.com.au/features/savers/">Up Bank</a> are taking to help their users not only manage money but also achieve their financial goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*9DGACB9YqZRFMz_f8OGt3g.png" /></figure><h3>Visibuild — a frustrating feed</h3><p>I’m not afraid to share that the first version of the <a href="http://visibuild.com.au/">Visibuild</a> home page is poor example of personalisation.</p><p>We wanted to create a home page that would allow our users to keep track of their assigned items but what we ended up with was a feed that actually made their lives harder as they were forced to endlessly scroll to find what they needed.</p><p>Luckily this was just v1 and we’ve been able listen to our customers feedback and iterate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/267/0*FKnEXLYAbL6OcGhe" /></figure><p>Our users are incredibly busy and the things they are trying to do differ depending on time of day and where they’re located: on their construction site or back in the office on their computer.</p><p>We went back to the drawing board to figure out exactly what our users need to do and how those things differ depending on role, time of day and their location.</p><p>This allowed us to redesign the home experience to offer personalised suggestions based on time and location making it simple for them to achieve their goals every time they open our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*P5NulQv7BltVVvWWnBzojA.png" /><figcaption>When a Visibuild user opens their app, their home page adapts based on what they need to do in the moment. Using quick actions and grouping their work into useful categories.</figcaption></figure><h3>How to personalise your product</h3><p>Personalisation can be as simple as greeting users by name when they first log-in, or as targeted as suggesting yoga classes to women at 9am on Saturday mornings in their area. The key involves making each of your users feel connected to your product and helping them achieve their unique goals.</p><h3>Personalisation approaches</h3><p>There are two key ways to think about personalisation (which can be combined):</p><ol><li><strong>Individual-based:</strong> Adapting the experience to suit the individual, their goals, interests or behaviour. Spotify’s <em>made for you</em> personalised playlists are a great example of this.</li><li><strong>Situation-based:</strong> Adapting to the users current situation when they open your product. Google is using situation-based personalisation to adapt transport suggestions based on whether your at home or work.</li></ol><p>The best examples of personalisation combine these two techniques to create a deeper experience suited both to the individual and their situation at a given time.</p><p><strong>Which factors can you leverage to deliver a personalised experience for your users?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*qIlWj8F9rGFuM0s5" /></figure><p>Every product is going to be different so the factors that influence your users and their situation might be different to those above. The key is to figure out what matters to your users in helping them achieve their goals.</p><h3>What does a typical day for your users look like?</h3><p>A really useful technique to map out which factors matter in your experience is to create a “day-in-the-life-of” timeline to showcase a typical day for your users. For your product it might make more sense to create a week, month or even year timeline.</p><p>The example below is a typical day for a Visibuild user and describes the times they need our product as well as everything else going on in their day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/0*D4tQU-qBQs5AeIhI" /><figcaption>A typical day for a Visibuild user, their goals change based on time of day, where they’re located and their device.</figcaption></figure><p>The powerful thing in this approach is that it forces you to zoom out from your own product journey’s and consider the big picture of someone’s day and how various factors impact what they are likely to do.</p><h3>Where to start? Start small.</h3><p>As you begin to map out all the ways you can add personalisation it might feel a little overwhelming. Where do you start? How much is too much?</p><p>My advice is to start small. Personalisation can go deep, but even the simple things will go along way in elevating the experience and helping be more successful.</p><p>Why not just start with welcoming them by name? Or provide personalised quick actions on their home page so they can quickly jump into what matters in the moment?</p><p>Personalisation is one of the most important techniques we have to make our users successful. Let’s move beyond transactional product experiences and instead follow the lead of our friendly local barista to make things personal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72a8fb7ad8ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visibuild/what-makes-good-products-great-make-things-personal-72a8fb7ad8ac">What makes good products great? Make things personal.</a> was originally published in <a href="https://medium.com/visibuild">Visibuild Product Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>