<?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 Ben Wakeman on Medium]]></title>
        <description><![CDATA[Stories by Ben Wakeman on Medium]]></description>
        <link>https://medium.com/@bwakeman?source=rss-93b215becbb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*YAvrMHyZLFddLVEx</url>
            <title>Stories by Ben Wakeman on Medium</title>
            <link>https://medium.com/@bwakeman?source=rss-93b215becbb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:06:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bwakeman/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[Everything You Ever Wanted to Know About Mobile Apps But Were Afraid to Ask]]></title>
            <link>https://medium.com/rightpoint-mobile-apps-guide/everything-you-ever-wanted-to-know-about-mobile-apps-but-were-afraid-to-ask-e8c64c414ba4?source=rss-93b215becbb------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8c64c414ba4</guid>
            <category><![CDATA[mobile-app-strategy]]></category>
            <category><![CDATA[mobile-app-best-practices]]></category>
            <dc:creator><![CDATA[Ben Wakeman]]></dc:creator>
            <pubDate>Wed, 14 Sep 2022 16:00:21 GMT</pubDate>
            <atom:updated>2022-09-14T16:39:03.907Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Girl and her cat watching something on her phone." src="https://cdn-images-1.medium.com/max/800/1*GGwzv-e_ngRNriOx3SIcxA.jpeg" /></figure><p>The mobile app as a channel has reached full maturity in the last few years. It’s no longer novel for most organizations, but essential. While there are some stellar mobile app experiences in every industry that set the bar, most organizations have mobile apps that struggle to meet the baseline for usability, utility, and user experience.</p><p>This Mobile Apps Guide is Rightpoint’s offering to help these organizations level up and unlock the potential of their mobile apps. Unlike other “thought leadership” pieces that smell as if they might be generated from the GP3 A.I. engine, the articles you will find in this guide are written by folks with deep, practical experience in designing, building, shipping, and maintaining mobile apps.</p><p>The insights and recommendations you will read here are grounded in the fifteen years of experience we’ve had in delivering mobile apps for clients. We have a comprehensive assessment framework we use to evaluate mobile apps across six dimensions:</p><ul><li><strong>Strategy</strong>: Is the value proposition clear and does it have market fit?</li><li><strong>Discover</strong>: How easy is it for potential users to find?</li><li><strong>Onboard</strong>: How easy is it for users to get in and experience the value?</li><li><strong>Engage</strong>: To what degree is that app actively incentivizing repeated use?</li><li><strong>Embed</strong>: To what degree has the app become essential to users?</li><li><strong>Measure</strong>: How mature is the app at using data and analytics to inform decisions?</li></ul><p>This framework is one we’ve used for years to help diagnose problems and uncover opportunities for our clients with mobile apps. In the past year, we’ve partnered with Google to provide these assessments for their leading customers with apps in the Play Store. What we’ve been learning we feel is too good to keep to ourselves.</p><p>We are rolling out this guide in six chapters, the first of which is Strategy. I hope the content helps you in your mobile app journey and please reach out with feedback or if you’d like to have a conversation about how Rightpoint might be able to help you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8c64c414ba4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rightpoint-mobile-apps-guide/everything-you-ever-wanted-to-know-about-mobile-apps-but-were-afraid-to-ask-e8c64c414ba4">Everything You Ever Wanted to Know About Mobile Apps But Were Afraid to Ask</a> was originally published in <a href="https://medium.com/rightpoint-mobile-apps-guide">Rightpoint Mobile Apps Guide</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anti-Patterns in Mobile App Strategy]]></title>
            <link>https://medium.com/rightpoint-mobile-apps-guide/anti-patterns-in-mobile-app-strategy-b38040782555?source=rss-93b215becbb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b38040782555</guid>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Ben Wakeman]]></dc:creator>
            <pubDate>Fri, 09 Sep 2022 20:35:00 GMT</pubDate>
            <atom:updated>2022-09-21T15:59:11.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XAmWiHSF15l9w8lJ6CiFEw.jpeg" /></figure><p>As helpful as a lot of good advice and positive models for mobile strategy can be, a few painful examples of what not to do can go a long way. These anti-patterns, like all anti-patterns, are typically not the product of poor strategic decisions, but usually the absence of strategy. If you see your mobile app falling prey to any of these patterns, there’s a good chance that your organization is not giving any priority to your mobile app and as a result doing more harm than good to your business.</p><h3>Wrapping Your Website is NOT a Mobile App</h3><p>The mobile web is a vital channel for most organizations. After all, with 90% of the population on planet earth browsing the internet from a smartphone, it’s the superhighway for information. Most organizations understand this and have put some investment into making their website experience at least mobile-friendly if not mobile first.</p><p>It’s easy to see why these same organizations might be tempted to leverage that functional or even beautiful mobile web experience by turning it into a mobile app. It’s easy enough to create the shell of a native Android or iOS app and stick a single web view in there that points to your website. Done! No fuss, no added expense.</p><p>For one thing, there’s a strong chance that Apple will reject your app as it does not meet its <a href="https://developer.apple.com/app-store/review/guidelines/">published</a> guidelines around minimum functionality requirements. In this document they clearly state:</p><p><em>Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the App Store.</em></p><p>Even if your website-in-an-app submission somehow gets approved, you should consider why Apple has this guideline to begin with. The point of a mobile app is not simply to be a vehicle for publishing content. Its intent is to provide some novel utility that has a purpose for persisting on someone’s mobile device. Should some of your customers actually go to the trouble to install your website-in-an-app, likely no good will come of it. In a best-case scenario, they use it once and never open it again. In a worst-case scenario, they write a blistering review in the app store, give you one star, and post on social media how pointless your app is.</p><h3>What about Hybrid Apps!?</h3><p>Hybrid is a woefully ambiguous term when it comes to apps, but when most people say they have a hybrid app, they mean it uses native app functionality and screens and uses some web content. Hybrid apps are a great solution in the following scenarios:</p><ol><li>You have a lot of HTML content residing in a CMS that’s mostly informational, but relevant and important to your customers when using your mobile app.</li><li>You have a complex and expensive workflow built for the web that you don’t have time/resources to adapt for a native mobile experience right away.</li></ol><p>With the exception of mobile-first businesses like games or FinTech apps, most organizations leverage some mix of native and web functionality. It can be a sound strategy, provided you don’t sacrifice user experience in one of the following ways:</p><ul><li>Launch users into web pages that are not mobile-friendly requiring them to pinch, zoom and scroll excessively</li><li>Launch users into web pages that have navigation bars</li><li>Launch users into a web view that allows them to unwittingly navigate out of your app</li><li>Orphan users in a web view where they either get stuck in a broken web experience or can’t return to your app navigation</li></ul><h3>You Might Not Need a Mobile App and That’s Okay</h3><p>Having a mobile app because every other company does is not a valid reason to have one. When you ask your customers to go to the app store and download an app, you need to be sure they will be delighted with the experience. The only way this will happen is if you have provided them with some valuable utility they could not get otherwise. For some businesses, a high-performing, beautiful mobile web experience is all that’s required.</p><h3>There is Such a Thing as Bad Publicity</h3><p>App store ratings and reviews have a huge influence on app adoption and yet, you would be surprised how many organizations don’t take them seriously. Most people will not consider installing a mobile app with anything less than three and a half stars. Further, most people will only look at the top three reviews and make their decision to download accordingly. So, if your most recent review is negative, it will deter new customers from installing your mobile app.</p><figure><img alt="50% of mobile users won’t consider downloading an app with a 3-star rating." src="https://cdn-images-1.medium.com/max/800/1*lefOYxd0MfBPCVFbKittCw.png" /></figure><p>It’s much easier to preempt bad reviews than it is to turn them around once they’re published to the app store. Companies like <a href="http://apptentive.com/">Apptentive</a> provide tools for actively capturing feedback and sentiment in your mobile app based on certain conditions, triggers, or behaviors that you define. In the event that one of your users encounters an error or crash while using your mobile app, <a href="http://apptentive.com/">Apptentive</a> can provide a prompt with an apology message and a comment field where the user can tell you what happened and express their frustration. In most cases, this is enough to prevent that user from logging into the app store and writing a nasty review.</p><p>You can also use proactive prompts to solicit positive ratings and reviews whenever you detect that a user has had a successful experience in your mobile app like completing a cart check-out or earning reward points. Without this type of preemptive strategy, your app will likely not get many reviews and the ones it does get will be predominantly negative. This is just the unfortunate reality. As consumers, we tend to be more motivated to provide feedback when we’re unhappy than we’ve had a good experience.</p><p>When someone does write a bad review of your mobile app in the app store, the worst thing you can do is ignore it. Both Apple and Google provide you with tools to publicly respond directly to reviews. Responding quickly and courteously to bad reviews does a couple of important things:</p><ol><li>It gives you an opportunity to learn more about what went wrong and how you can address it for this and other users in a subsequent release.</li><li>It demonstrates to any future readers of your reviews that you care about customer experience and that you are actively working to make it better.</li></ol><h3>Infrequent and Irregular App Releases</h3><p>Consistency and persistence are hard. These qualities are the foundation for success in most things whether it’s eating healthier, raising children, or saving money. They are equally important when it comes to your mobile app releases. If you only update your app once or twice a year or you do it with more frequency, but not on a consistent schedule, you will lose customers and create chaos in your mobile product teams. Shipping daily releases like Facebook and other big tech companies do is not necessary for most organizations but waiting longer than a month to push out a new release of your mobile app is detrimental for several reasons.</p><p>While the concept of Continuous Integration/Continuous Deployment or CI/CD is not new, a surprising number of organizations with mobile apps have not adopted the strategy. Either they’ve not invested in the necessary tools, or they don’t properly use them. Releasing is stressful for your mobile team. They’ve worked for days, weeks, maybe, but hopefully not months on getting everything perfect to ship the latest build of your mobile app out to the public. About a million things could go wrong and once it’s out there, any issues will be experienced by all your active users. It’s enough to make you want to never release. There’s a strong incentive to procrastinate. But that’s the absolute worst strategy and here’s why.</p><p>The more frequently you release a version of your mobile app, the fewer things can go wrong. Fewer changes mean less code which means fewer bugs. Additionally, the many procedural steps required to get a new release candidate through your pipeline and published to the app stores become routine for your team. They won’t have to dust off the manual every time and sweat bullets as their cursor hovers over the publish button. They will have confidence and be familiar with the process.</p><p>There is one additional and significant benefit that comes with frequent, regular mobile app releases. With every new release, you can fix issues or add functionality that your customers might have complained about previously in app store reviews. When you respond to those reviews personally and tell them their issues have been fixed, it builds a tremendous amount of goodwill which has a halo effect on future readers of that review.</p><p><em>Want help with your mobile app? The Rightpoint Digital Product team would love to learn more about the challenges your facing. </em><a href="https://www.rightpoint.com/landing-pages/mobile-app-development?utm_source=Medium&amp;utm_medium=Content&amp;utm_campaign=Mobile%20Field%20Guide"><em>Please reach out so we can set up a chat</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b38040782555" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rightpoint-mobile-apps-guide/anti-patterns-in-mobile-app-strategy-b38040782555">Anti-Patterns in Mobile App Strategy</a> was originally published in <a href="https://medium.com/rightpoint-mobile-apps-guide">Rightpoint Mobile Apps Guide</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Go Further When We Go Together]]></title>
            <link>https://medium.com/rightpoint-mobile-apps-guide/we-go-further-when-we-go-together-567837989891?source=rss-93b215becbb------2</link>
            <guid isPermaLink="false">https://medium.com/p/567837989891</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[mobile-app-strategy]]></category>
            <category><![CDATA[mobile-apps-guide]]></category>
            <dc:creator><![CDATA[Ben Wakeman]]></dc:creator>
            <pubDate>Tue, 06 Sep 2022 15:33:41 GMT</pubDate>
            <atom:updated>2022-09-19T20:56:11.042Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CHtgFDAI9qUIcjYrGMmaXw.jpeg" /></figure><p>“Let’s all do our own thing and hope for the best,” said no leader ever but that’s exactly what you see in many companies when it comes to their digital strategy and unsurprisingly it’s likely the biggest reason why those companies struggle to retain talent and deliver great digital experiences for their customers.</p><p>Mobile apps are like human babies, they need constant care, feeding, monitoring, and support. They need a steady flow of new challenges to learn, and they need engagement from others to grow. So, just as it takes a village to raise a child, it takes a connected group of collaborators to create a successful mobile app.</p><h3>Lost in the Labyrinth</h3><p>At <a href="https://www.rightpoint.com/landing-pages/mobile-app-development?utm_source=Medium&amp;utm_medium=Content&amp;utm_campaign=Mobile%20Field%20Guide">Rightpoint</a> we’re fortunate to have the chance to see the inner workings of all types of organizations across a wide range of industries when we’re engaged to help with their digital experiences. Often, we end up working right in the middle of several business units, typically IT and Marketing, but sometimes Product, Sales and Finance are in the mix, depending on the type of business and the application we’re helping develop. It is the rare exception where these different groups are truly aligned to a purpose and have a healthy collaboration established.</p><p>It’s not hard to understand why. The folks within these groups are not malevolent forces of chaos bent on world domination, though that’s how they may feel about each other in more toxic corporate cultures. The simple truth, in most circumstances, is that it’s the game that’s broken, not the players. The players are just following the rules that were established long before they were hired. Obviously, the rules were never intentionally crafted or communicated through a Powerpoint or a Company All Hands. The rules we’re talking about here are anti-patterns, the result of a thousand minor disagreements, miscommunications, and misinterpretations of what truly matters for the company. Over time, these anti-patterns harden into a concrete labyrinth from which no idea, no matter how good can escape.</p><blockquote>It is accurate to describe these broken organizations as a labyrinth because the players inside can’t see the way out, only the choice that’s immediately in front of them.</blockquote><p>When <a href="https://www.rightpoint.com/landing-pages/mobile-app-development?utm_source=Medium&amp;utm_medium=Content&amp;utm_campaign=Mobile%20Field%20Guide">Rightpoint</a> parachutes in, we have the advantage of a bird’s eye view and can see with objectivity the elaborate and impenetrable walls that have been built. Often, people stuck in these hedgerows are smart, highly motivated individuals who understand the problem clearly, but are powerless to change things. Regardless of how things got that way, the first step toward fixing them is surprisingly simple.</p><h3>Bring it In</h3><p>In any Labyrinth, no matter how intricate, there is a central courtyard where all paths terminate. For companies trapped in the labyrinth of their own corporate culture, the way out is actually <em>the way in</em>. When we’re successful working with clients, we’re able to guide the folks toiling away in the outer reaches of the labyrinth within their own business units into the center where they can gather in a circle and not just see one another but more importantly, see the customers they are trying to serve. While delightful, a metaphor only gets us so far. Let’s look at a practical example.</p><h3>Mobile is a Lot to Get Right</h3><p>In many corporate structures, it’s IT who’s been charged with owning the mobile app. It makes sense. A mobile app is a very technical thing. But it’s more than a bunch of code compiled into a binary file. Today it’s often THE primary funnel a business has for acquiring, serving, and supporting their customers. It must be compelling. It must be elegantly designed. It must represent the primary offering that keeps a company in business. It must be fast. It must be 100% accurate. It must always work from any place at any time of day, sometimes in any part of the world. It must constantly evolve with the needs of customers and the technological platforms it’s built upon. And one last thing, if it doesn’t do all these things, customers will leave a one-star review in the app store, delete it, and never come back. No pressure.</p><figure><img alt="Illustratrive photo of bearded man screaming in frustration with his hands over his ears." src="https://cdn-images-1.medium.com/max/1024/1*-fRbR8YF_0aBsut_-d6AbQ.png" /></figure><p>No wonder IT is so grumpy all the time. Over the hedgerows of the labyrinth, they hear marketing shouting about something called a <em>value prop</em> and designers imploring about the <em>weight</em> of typography. There are plenty more voices too, some louder than others calling for conversion metrics, customer sentiment capture, and agile practices. It’s easy to see how the walls just get higher, the mobile baby gets neglected, employees quit, customers leave, revenue drops, and C-Suites become revolving doors. Mobile apps are complicated, and they can’t thrive without true collaboration.</p><h3>Enter Product Thinking</h3><p>Once we lead this cacophony of voices from the far reaches of the corporate labyrinth to the meeting table at the center, we have a conversation about how things can change. How, you ask? By beginning to think about the mobile app as a product that can only be successful when IT, Marketing, Creative, Sales, etc. can come together with a unified <a href="https://medium.com/rightpoint-mobile-apps-guide/start-with-a-mobile-vision-dd4ebd9393ae">vision</a> and <a href="https://medium.com/rightpoint-mobile-apps-guide/clear-goals-drive-clear-results-130c5d200930">goals</a> that are grounded in serving customer needs.</p><p>It’s at this point that there’s an eye-opening opportunity in the conversation to hear everyone’s opinion about what their customers’ needs are. In most cases, everyone regardless of their role in the organization has a piece of the puzzle, but it can’t really be put together yet. The piece that’s usually missing is the actual voice of the customer. It’s an easy mistake to think that you are the user/customer, so you know best, but it’s an expensive mistake. Customers are always changing and adapting to changes in the world, new technologies, inflation, and pandemics.</p><p>Many organizations don’t want to slow down to do user research or maybe they don’t want to pay for it. They would rather use the money on development. Again, it’s another expensive mistake to make. The investment of good research will always pay dividends when you release a new version of your mobile app that is informed by insights from your customers.</p><h3>Product Managers are Drivers Who Ask for Directions</h3><p>Understanding customer needs is the foundation for becoming product-led when it comes to your mobile app but there is much more to it. The best way to become product-led is to hire a great product manager. But the role of Product Management is often misunderstood and there are about as many different definitions of it as there are organizations who hire for the role.</p><p>As a manager of product managers, I think a lot about the role and what its real value is. I’ve learned 95% of what I know about product management from the product managers I’ve managed because I ask a lot of questions. The fundamental value of a good Product Manager is the ability to ask a lot of questions. They are curious guides who know they don’t have all the answers but must ask the right questions and listen closely. Great product managers are also gifted communicators and consensus builders who refuse to let politics, process, or protocol get in the way of the right solution which is always the result of superior collaboration.</p><h3>Staying Out of the Labyrinth</h3><p>Just because you’ve changed some things, you can’t expect old habits to just go away forever. The best tools for keeping the walls from going up again in your organization are:</p><ul><li><strong>Transparency</strong> — show your work and insist on a culture where everyone does the same</li><li><strong>Inclusion</strong> — invite everyone’s input and feedback regardless of their title</li><li><strong>Customer Needs</strong> — kept in mind, this will never steer your organization wrong</li><li><strong>Business Goals</strong> — kept in mind, focus everyone on what matters and what doesn’t</li><li><strong>Ego-Free</strong> — the best ideas are just as good when they’re not yours</li></ul><p>If you can leverage these tools and incorporate them into your mobile product team’s culture so they become the norm, everything will begin to improve. Your people will be happier and more motivated. Your customers will be happier because you’re listening to them. Management will be happier because business is improving.</p><p><em>Want help with your mobile app? The Rightpoint Digital Product team would love to learn more about the challenges your facing. </em><a href="https://www.rightpoint.com/landing-pages/mobile-app-development?utm_source=Medium&amp;utm_medium=Content&amp;utm_campaign=Mobile%20Field%20Guide"><em>Please reach out so we can set up a chat</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=567837989891" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rightpoint-mobile-apps-guide/we-go-further-when-we-go-together-567837989891">We Go Further When We Go Together</a> was originally published in <a href="https://medium.com/rightpoint-mobile-apps-guide">Rightpoint Mobile Apps Guide</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clear Goals Drive Clear Results]]></title>
            <link>https://medium.com/rightpoint-mobile-apps-guide/clear-goals-drive-clear-results-130c5d200930?source=rss-93b215becbb------2</link>
            <guid isPermaLink="false">https://medium.com/p/130c5d200930</guid>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Ben Wakeman]]></dc:creator>
            <pubDate>Tue, 06 Sep 2022 15:23:38 GMT</pubDate>
            <atom:updated>2022-09-19T18:15:03.899Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-N8sRUCKAWXs9lFapR0-mg.jpeg" /></figure><p>Everyone agrees that goals matter. Most organizations invest a lot of time and create complicated frameworks to facilitate setting goals for individuals, project teams, practices, business units, and for the entire organization. But often, it seems all the focus and energy for goals is expended upfront identifying and agreeing on goals, then drops off a cliff after that. As a result, most of us don’t really believe in goals anymore, or at least we don’t believe they can drive the outcomes they promise. They can feel performative.</p><p>In collaborating with many clients to deliver mobile solutions over the years, I’ve seen a wide spectrum of goals. They range from invisible to so incredibly complex and overly ambitious that teams can’t even explain them, much less convert them into action. It doesn’t have to be this way. Goals can be a powerful tool for bringing focus and shutting down the noise that competes for a busy mobile product team’s attention. But to do that, they must feel <em>inevitable</em> and be so simple and clear that every single person on the team can state them by heart and use them as a lens through which they focus their work every day.</p><h3>Goals by Committee Don’t Work</h3><p>Keeping your goals simple and direct seems obvious, but it’s hard to do in practice. There is a lot of handwringing around setting goals because so much is riding on them and often, too many contributing opinions. All too quickly your goals can turn into a manifesto when what you really need is three well-crafted bullets.</p><p>The first step to keeping it simple is to not set goals for your mobile app by committee. The goals for your mobile app should be set by the business stakeholder who is accountable for the success of the app. To do this effectively, this individual needs the following:</p><ol><li>A clear grasp of the organization’s current strategy and goals</li><li>Baseline metrics for how the app has performed historically</li><li>Deep understanding of the mobile apps channel and the specific opportunities it lends to your organization’s product or service</li></ol><p>Armed with this knowledge they should be able to create at least the first draft of goals for the mobile app that can be shared and refined based on feedback from the Product Management, Design and Technology leads on the team.</p><h3>Simple, Direct, and Measurable</h3><p>Effective goals should be written with clear, direct language. There’s no need to overload a goal with exposition or execution-level details. The goal’s only purpose is to communicate what it is, not where it came from or how it should be accomplished. The mobile team should already understand your organization’s top-line strategy and should be able to easily understand how the goal fits into it. It should be up to the team to figure out the specific initiatives to accomplish the goal. Product teams love a meaty problem to solve, so don’t prescribe a solution in the wording of your goals.</p><p>Let’s look at an obnoxious example to demonstrate how a goal can collapse under its own weight.</p><p><em>In BroLand’s mission to be the #1 brokerage for NFTs we need to expand the size of our addressable market by engaging the 25 to 40-year-old female demographic. To achieve this, we will add more pictures of kittens, puppies, and bottles of Rosé</em> <em>which should increase the number of daily active users in our mobile app by 20% by the end of Q2.</em></p><p>While exaggerated (and offensive) to make a point, this example provides an unnecessary amount of background on the goal and prescribes a solution. Not only will your team hate you for this goal, but they will likely not remember anything about it because it was too complicated. The business owner crafting this goal will need to think through all this background and ruthlessly prioritize objectives to arrive at the goal, but the goal itself should not show all this consternation. Let’s look at a tidier version of the same goal:</p><p><em>Increase daily active users in the mobile app by 20% by the end of Q2.</em></p><p>This version gets the job done. Does it answer the why or give more context about the what? No, but these things will be obvious to your team. The important thing is they have a metric to move and a deadline. Having these two things will help focus every ideation and planning session.</p><h3>One Big Goal and Two for Support</h3><p>From what I’ve written so far, you may be thinking, “well, this is easy, I only ever need to write three goals: increase revenue, increase adoption, and increase retention. Done!” While you’re not entirely wrong, there’s more to it than that. At a business health level, there are ultimately just a handful of metrics people care about, but there are many ways to slice these and distribute them across an organization and its digital channels. Asking the mobile team to drive all the metrics up at the same time quarter over quarter is as effective as giving them no goals at all.</p><p>A better approach is to issue one big, audacious goal that drives an important business metric for the mobile app and supplement it with a couple of more specific goals that support it. For example:</p><ol><li><em>Increase daily active users in the mobile app by 20% by the end of Q2</em></li><li><em>Increase user engagement with the NiftyDesigner feature by 50%</em></li><li><em>Increase app launches from promo push notifications by 25%</em></li></ol><p>Goal number one is a big lift for a quarter by any standard, but it will focus your team to nudge them out of their comfort zone. You can think of goals two and three as booster rockets for the main goal. While they can and should each be measured on their own merit, they directly contribute to increasing daily active users.</p><p>There are side benefits of these two supporting goals that amplify their value. BroLand’s VP of Mobile Product will have a way to focus the team’s attention on improving the NiftyDesigner feature and a way to measure its value to their users. The company’s under-utilized promotional content engine will also get some love and the team will have a chance to refine how they surface promotions through push notifications. You can begin to see how these three simply stated goals will have ripple effects throughout the organization and drive deeper collaboration with other business units at BroLand.</p><h3>Reflect, Learn, and Improve</h3><p>The painful truth is that you will sometimes fail to meet even the most perfectly crafted, right-sized goals for your mobile app. No one can see the future, predict pandemics, market crashes, or changes Apple may make in the next version of iOS. But the beauty of having a solid set of goals is that you can learn as much when you fail as when you succeed.</p><p>When you fail, have a post-mortem with your team, and be sure you’ve established a safe space for them to talk candidly about what went wrong and why. What did you learn about the updates you made to the toolbar in NiftyDesigner? Maybe iconography without labels was the wrong move and your analytics reporting shows that. Now you have something clear and actionable to change and hopefully improve in the next release which will drive the uptick in engagement you set out to achieve.</p><p>Like everything in the process of making digital products, goal setting is an evolving, iterative process. Establishing norms around setting goals, measuring their effectiveness, and evolving them over time will ultimately drive growth.</p><p><em>Want help with your mobile app? The Rightpoint Digital Product team would love to learn more about the challenges your facing. </em><a href="https://www.rightpoint.com/landing-pages/mobile-app-development?utm_source=Medium&amp;utm_medium=Content&amp;utm_campaign=Mobile%20Field%20Guide"><em>Please reach out so we can set up a chat</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=130c5d200930" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rightpoint-mobile-apps-guide/clear-goals-drive-clear-results-130c5d200930">Clear Goals Drive Clear Results</a> was originally published in <a href="https://medium.com/rightpoint-mobile-apps-guide">Rightpoint Mobile Apps Guide</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Start with a Mobile Vision]]></title>
            <link>https://medium.com/rightpoint-mobile-apps-guide/start-with-a-mobile-vision-dd4ebd9393ae?source=rss-93b215becbb------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd4ebd9393ae</guid>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Ben Wakeman]]></dc:creator>
            <pubDate>Thu, 01 Sep 2022 17:42:37 GMT</pubDate>
            <atom:updated>2022-09-19T20:53:43.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rebRZ_8yXGYfGBhSeA0BLQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@pawelskor?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Paul Skorupskas</a> on <a href="https://unsplash.com/s/photos/vision?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Vision is a loaded word that has earned an eye-roll response for many of us who have been handed “visions” that are as vague as they are unrealistic and unachievable. So, I approach this entreaty to show the value of a good vision with more than a healthy measure of skepticism.</p><p>A great product vision strikes the perfect balance between aspirational and achievable. The common metaphor applied when people talk about strategy and vision is a north star. While great for general navigational purposes and for identifying the big dipper, I would aim for something closer to the horizon, something that your team can understand and be inspired by but is also easy to break down into actionable work that can be measured.</p><p>The product vision for your mobile app shouldn’t be a 30-slide Powerpoint or even a one-pager document. The beauty of a great vision is that it can be communicated in a well-crafted statement that is easily understood by all. Here are the key ingredients:</p><ul><li>What is your product?</li><li>Who is it made for?</li><li>Why will they love it?</li><li>Why is it better than any other alternative?</li></ul><p>That’s it. Let’s look at an example.</p><blockquote><em>The Procrasdonation app is for people who feel guilt and anxiety about failing to prioritize and complete important goals. The app allows them to assign a dollar amount to a goal along with a deadline and when they fail to meet the deadline, that amount is automatically donated to a charity of their choosing. Unlike other methods for tracking goals like to-do lists, Procrasdonation combines a tangible penalty and reward mechanic that users will love because it motivates them to better themselves but improves the lives of others even when they fail.</em></blockquote><p>This vision statement distills the essence of the product and its value to users with unambiguous language. This app (if it existed) is likely a lot more complex than what is described here, but these three sentences tell the complete story. There’s the protagonist, their conflict, the proposed solution, and the dénouement. If your vision statement runs longer than three sentences, you are probably too far in the weeds.</p><p>Let’s look at a less effective example of a product vision.</p><blockquote><em>Procrasdonation is an app that helps people achieve their goals while also giving back to the community. The app will transform the way people think about and prioritize their goals because it introduces a whole new way of thinking about them.</em></blockquote><p>This version attempts to do some of the work of a good vision statement but fails to tell the complete story because it doesn’t explain the core function of the app and how it specifically addresses a user’s problem in a way that is different than any other alternative. Simply stating that something will be loved by people is not an effective story. Showing how and why it will be loved is the key ingredient for a good story and by extension a good vision statement.</p><figure><img alt="Cartoon illustration of cave people talking. For pre-agricultural hominids who want to eat, Bow&amp;Arrow is a weapon that kills food. Unlike long, sharp stick, Bow&amp;Arrow is compact, portable and may be used from a safe distance." src="https://cdn-images-1.medium.com/max/936/1*BlHkgoc9cAYb5PFU4nLK8Q.png" /><figcaption>Original art by David Counts.</figcaption></figure><h3>What does a great product vision do for your mobile app strategy?</h3><p>Most importantly, it puts your users and their needs at the center of the story and keeps them there as a constant reminder. Marketing may want to shove a lot of extra content into the app that gets in the way of users completing their primary goal. Finance may push you to take a higher percentage as a “service fee” which you know will undermine trust with your users. Your product vision is the contract you have to ward off these requests and protect what is the heartbeat of any successful mobile app: happy users.</p><p>The process of collaboratively crafting the vision statement for your mobile app forces your leadership team to agree on exactly what matters most and how to communicate that in a way that every person in your organization can understand and rally behind. Given the complexity of conceiving, designing, developing, releasing, and marketing a mobile app, it is easy for an organization to miss the forest for the trees.</p><p>Your engineers could have a strong opinion that Procrasdonation users should be able to create sub-tasks beneath their goals and only be penalized a percentage when they fail to meet the deadline. Designers may insist that the app provides no onboarding experience because they think their UX design is intuitive enough. Your product manager may be trying to force you to create an MVP that is so spare it doesn’t demonstrate enough value for new users to care. Problems can compound quickly in a product team as different disciplines bring their points of view to bear, and you may find yourself with a mobile app that is so far from what it was intended to be.</p><p>What a strong vision provides is a way to filter out anything that does not directly drive towards achieving that vision. In any of the scenarios mentioned above, any team member can bring out the vision statement and ask the simple questions:</p><ol><li>“how does _______ help us accomplish this vision?”</li><li>“how could _______ put the vision for our app at risk?”</li></ol><p>The answer to these questions will still be a debate, maybe even a lengthy one, but at least you have some solid boundaries to help focus the discussion. If everyone understands the atomic core of your product, they will be less inclined to contribute ideas that muddle that value.</p><h3>How do you create a vision?</h3><p>Like most meaningful initiatives we tackle with work, crafting a vision for your mobile app should incorporate a diverse team from different disciplines who all care very much about the thing you are making. In most cases a product vision can be accomplished in a two to three-hour workshop provided you have invited the right people and those people are prepped with the following:</p><ul><li>The goal of the workshop</li><li>The ingredients of a product vision</li><li>Examples of great vision statements</li><li>Understanding your users’ needs</li><li>Understanding your app’s core value proposition</li></ul><p>At <a href="https://www.rightpoint.com/landing-pages/mobile-app-development?utm_source=Medium&amp;utm_medium=Content&amp;utm_campaign=Mobile%20Field%20Guide">Rightpoint</a>, we facilitate these workshops in nearly every engagement, regardless of whether it’s a brand-new mobile app or a redesign of one that’s existed for years because it is the single best way to get a team to come together and reach a consensus on where we will focus all our energy in the coming months. While it’s ideal to conduct these in person around a whiteboard with stickies, we’ve had great success using remote collaboration tools like Miro. Whoever facilitates the workshop should keep a few important principles in mind:</p><ul><li><strong>Encourage writing thoughts down</strong> as opposed to shouting them out when you’re in the generative/ideation stage. This levels the playing field so that the senior-most or most extroverted individuals don’t dominate.</li><li><strong>Listen for opposing points of view and</strong> explore them fully. This should be a safe place for anyone to challenge assumptions about the purpose of your app. The best visions are chiseled with nuance that comes from healthy debates.</li><li><strong>Delegate someone to be the scribe</strong>. Good writing is not done by a committee so elect a strong writer within your group to write and iterate on the actual vision statement throughout the discussion.</li><li><strong>Get 100% buy-in</strong> before everyone leaves the workshop. Silence is not agreement. If someone is not vocally onboard with the vision encourage them to speak up. Silent consent can quickly turn into destabilizing descent in the future.</li></ul><p>Finally, while your mobile app’s vision is important it’s not immutable and etched in stone. Over time, you can and should revisit the vision. With any luck, your product will grow and become too big for a single vision statement to cover everything it can do for your users. When this happens, you might find it useful to craft separate visions for different feature areas.</p><p><em>Want help with your mobile app? The Rightpoint Digital Product team would love to learn more about the challenges your facing. </em><a href="https://www.rightpoint.com/landing-pages/mobile-app-development?utm_source=Medium&amp;utm_medium=Content&amp;utm_campaign=Mobile%20Field%20Guide"><em>Please reach out so we can set up a chat</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd4ebd9393ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rightpoint-mobile-apps-guide/start-with-a-mobile-vision-dd4ebd9393ae">Start with a Mobile Vision</a> was originally published in <a href="https://medium.com/rightpoint-mobile-apps-guide">Rightpoint Mobile Apps Guide</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>