<?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 Lyndon Maher on Medium]]></title>
        <description><![CDATA[Stories by Lyndon Maher on Medium]]></description>
        <link>https://medium.com/@lyndonmaher?source=rss-2bc9c2ce19f4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4tZa_yVJrU07G64G_wY7Mw.jpeg</url>
            <title>Stories by Lyndon Maher on Medium</title>
            <link>https://medium.com/@lyndonmaher?source=rss-2bc9c2ce19f4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:26:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lyndonmaher/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[Great product managers know how to say 'No']]></title>
            <link>https://lyndonmaher.medium.com/great-product-managers-know-how-to-say-no-19361e92bc71?source=rss-2bc9c2ce19f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/19361e92bc71</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Lyndon Maher]]></dc:creator>
            <pubDate>Thu, 02 Apr 2020 00:05:26 GMT</pubDate>
            <atom:updated>2021-04-28T06:06:11.167Z</atom:updated>
            <content:encoded><![CDATA[<h3>Great product managers know how to say ‘No’!</h3><p>Any company that wants to stay relevant is constantly generating new ideas. Guess where most of these end up? You got it — the product team. A recent survey of first-year product managers found that one area they struggled with most was responding to never-ending feature requests. Trying to do it all isn’t only impractical, it’s also near impossible. That’s why being able to effectively say ‘No’ is so necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-ft98hQL4aWhAYSA9dfEg.jpeg" /><figcaption>Learn to be comfortable saying no….. and with a smile.</figcaption></figure><p>In my very first product role, I was inundated with requests.</p><p>I quickly found that I needed to say ‘No’ more than ‘Yes’. Before long I became “Lyndon the ‘No’ guy”. Not exactly how I wanted to be known.</p><p>I soon realised the importance of helping stakeholders to understand why I was saying ‘No’. With experience, I learned how to do this in a way that strengthened relationships as well as outcomes. Here are five techniques that might help you.</p><h3><strong>1: Reframe immediately</strong></h3><p>You’ve probably noticed that most requests come to your product team as defined solutions. It can be easy to get caught up in the proposed solution. But take a moment to step back and ask questions. What is the problem being addressed? What is the objective? Does it relate back to the vision and strategy?</p><p>With the full context, you might find that the light bulb goes off. Perhaps it’s an issue your team is aware of and already focused on solving. Great! Although the solution might be different to what your stakeholder has in mind, it’s still underway. So saying ‘No’ becomes a positive conversation.</p><p>I’ve found that taking the time to understand problems is essential. By doing so, sometimes you’ll even expose problems that haven’t been fully considered. That can be a huge opportunity for you and your product!</p><h3><strong>2: Leverage the data</strong></h3><p>When someone casually asks you in the elevator what you’re working on, your response probably starts with ‘I’. That’s fine. But when reviewing a request, you want to avoid this. No one likes feeling that a ‘No’ is just personal opinion. That’s where the data becomes your best friend. By referring to the data, you can offer an unbiased response that moves the conversation away from you.</p><p>Your roadmap is another trusty sidekick. Chances are that every item on your roadmap earned its place because the data showed it would have the biggest impact. When a stakeholder wants to focus on something that’s not on the roadmap, the data will help you discuss the priorities and weigh up the request based on its potential impact.</p><p>You can also use data to assess new requests. If the data shows it won’t have a significant impact, this becomes an easy ‘effort versus reward’ explanation. Or better yet, you may just uncover a hidden gem!</p><h3><strong>3: Use a simple roadmap</strong></h3><p>Sometimes you need to give an immediate response. My go to is, ‘Not right now’. And having your roadmap handy is a great visual way to justify your answer.</p><p>Your company will only have a certain amount of bandwidth during any particular period. With your roadmap, you can visually show what’s critical and in progress right now, what’s planned and ready to start immediately after, and what’s being considered beyond that.</p><p>It helps to re-iterate why current initiatives are a focus. If you have your prioritisation on point, your stakeholder won’t want to disrupt the great work that is going on. It also shows that you would need to change a priority to accommodate their request. I almost always commit to placing the request in the consideration bucket, which allows time to evaluate the request and collect more data.</p><p>Just one thing to note. I know that many companies use OKRs. I’m not suggesting that the roadmap replaces these. It’s just an effective visual tool for prioritisation conversations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBkJEWxz3Eny_IyZ9j3ZPQ.jpeg" /><figcaption>Capturing a new request so that it’s considered for the future is a technique to consider when saying No.</figcaption></figure><h3><strong>4: Run a small-scope experiment</strong></h3><p>Let’s face it, there will be times when it’s just not possible to shut down an idea completely. So the challenge becomes finding a way to demonstrate progress without completely derailing your roadmap.</p><p>Something that works well is re-scoping the request to a small experiment where you can test a hypothesis. By gathering more data and understanding the user value, you can inform future work. And you can run the test without chewing up valuable engineering resources. One approach is using tools such as Optimizely or Google Optimize.</p><h3><strong>5: Explore trade-offs</strong></h3><p>Not everything has to be developed in-house or fully polished. Another option could include exposing a new API endpoint. Or, if you don’t have an API, you may want to build one so you’re able to outsource to third parties when needed. You could also explore temporary workarounds, such as using third-party software or a clever manual solution.</p><h3><strong>Say ‘No’ without becoming “the ‘No’ guy”</strong></h3><p>It’s never easy to be the bearer of bad news. But these techniques will help you maintain positive relationships with your stakeholders while still saying ‘No’. When it comes down to it, your team and your stakeholders just want the best for the business. So showing that you’re saying ‘No’ with the business’ best interests and priorities at heart is sure to soften the blow.</p><p>And these are just a few pointers — I would love to hear your tips for saying ‘No’.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19361e92bc71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evolving as a product manager — sharing 5 lessons]]></title>
            <link>https://lyndonmaher.medium.com/evolving-as-a-product-manager-sharing-5-lessons-5a1f85fc841b?source=rss-2bc9c2ce19f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a1f85fc841b</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[job-hunting]]></category>
            <dc:creator><![CDATA[Lyndon Maher]]></dc:creator>
            <pubDate>Thu, 29 Nov 2018 03:12:39 GMT</pubDate>
            <atom:updated>2018-11-29T03:12:39.605Z</atom:updated>
            <content:encoded><![CDATA[<h3>Evolving as a product manager</h3><p>We’re lucky enough to work in an industry that is ever-changing. And it gives us a certain freedom to push our careers in many directions. I recently shared a few tips from my own career in a 5 minute lightning talk at a <a href="https://www.meetup.com/Product-Mavens/">product meetup</a>, I wanted to write them down and share them here for others.</p><p><strong>Moon-shot jobs. Know and close the gaps</strong></p><p>Shoot for your dream job. When I was moving into product management, I had a Google drive where I saved the “moon-shot” jobs. These were job descriptions of my ideal roles at companies like Twitter, Facebook and Google. Next I identified the key gaps I needed to close before applying for those roles. This included learning about analytics and building strong expertise in User Experience design and mobile app development. Then I set about acquiring the additional skills that I wanted.</p><p><strong>Read “The first 90 days”</strong></p><p>An amazing manager of mine bought me<a href="https://www.amazon.com/First-90-Days-Strategies-Expanded/dp/1422188612"> this book</a> after I had landed a new product manager role. It’s a great read and something I went back to each time I landed a new role or promotion. A key point is around the mental shift you need to make when starting a new role. For me, that really hit home given I was moving from corporate to a startup.</p><p><strong>Seek out mentors</strong></p><p>As I moved into more senior roles, I realised how much I had learnt from the people I had worked with. So I got proactive about scaling my learning. I reached out to people who were at a similar point in their career to me, or slightly further along. To expand the breadth of my knowledge, I looked for mentors from alternative industries and varied business models. It’s amazing how much you can learn over a cup of coffee. I also asked each mentor if they could recommend someone else I should meet and give me a warm introduction. In the same way, I also do my best to say yes to helping out other product managers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*vYJ_kJA13IyWOn44KuRLSg.png" /><figcaption>It’s amazing what you can learn from someone by buying them a coffee.</figcaption></figure><p><strong>Keep learning &amp; sharing</strong></p><p>I feel like the more I learn and the more I experience through building products, the more there is to learn. There are always so many exciting industry developments that help us grow. Recently I listened to this<a href="https://twitter.com/lyndon_maher/status/1062289808368664577"> great podcast</a> a friend recommended — it’s packed with nuggets of wisdom. I love listening to podcasts, youtube videos and attending meetups from those in our industry. And I really enjoy speaking at meetups and events, so I can give back to our industry and helps others in their careers.</p><p><strong>Define your principles</strong></p><p>Setting out my own set of principles is a recent focus of mine. It led me to the book “<a href="https://www.amazon.com/dp/1501124021/ref=cm_sw_r_tw_dp_U_x_2t1.BbKDVDCMM">Principles: Life and Work</a>,” which is by the founder of the hedge fund Bridgewater. Now that I’ve moved into consulting and advising, I want clarity around how I operate in a way that I can easily share with clients. I can also see that, as a manager, this is really beneficial to share with a team. I’m new to this so I am excited to see how this is received with others.</p><h3>Alex Roe on Twitter</h3><p>Updated my product management principles doc after my first 6 months as the first PM at an enterprise startup; lots of learnings after being in the consumer product (+ large company) world. https://t.co/0QSj7RK7gh</p><p><strong>Take your skills to the next level</strong></p><p>On top of the things you do on a day-to-day basis to push your abilities forward, it’s also great to pick up some structured training along the way. If you’d like to accelerate your growth as a product manager, you may want to take part in my upcoming “<a href="https://zambesi.com/course/product-management/lyndon-maher">Good to great product management</a>” workshop.</p><p>And sharing knowledge within our industry helps us all. So please leave a comment with any stand-out books you’ve read or learnings you’ve picked up along the way.</p><p>Follow me on twitter: <a href="http://www.twitter.com/lyndon_maher">twitter.com/lyndon_maher</a></p><h3>Terem Technologies on Twitter</h3><p>@lyndon_maher talking about @RayDalio&#39;s Principles book and sharing those principles with others but adapting to your environment too #product @liz_kaelin</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a1f85fc841b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 ways product managers can draw inspiration from Picasso]]></title>
            <link>https://lyndonmaher.medium.com/4-ways-product-managers-can-draw-inspiration-from-picasso-2a13870d96ea?source=rss-2bc9c2ce19f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a13870d96ea</guid>
            <dc:creator><![CDATA[Lyndon Maher]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 22:17:08 GMT</pubDate>
            <atom:updated>2018-08-22T22:17:08.811Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Kh8TzABRb5lAqAz69Ftnw.jpeg" /></figure><p>If you’ve ever visited an art museum, you probably noticed that each artist has a unique way of seeing the world. This is never more true than when you find yourself in front of a Picasso. It’s no wonder that Apple runs an internal training program teaching staff to design products the ‘Picasso way’. So how can Picasso help you breathe innovation into your product design management practice?</p><p>Firstly, it’s worth mentioning that Picasso could paint realistic masterpieces like the best of them. He just chose not to. Working within such constraints didn’t allow for enough creativity and perspective.</p><p>It’s exactly that kind of explorative and creative thinking that drew me to product management. And we need to keep our thinking fresh. That’s why I found myself looking to the creative masters for inspiration. Here are four Picasso’s quotes to fire up your innovative thinking.</p><h3><strong>“Bad artists copy. Good artists steal.”</strong></h3><p>At first glance, this sounds underhanded. But the philosophy is sound. Picasso meant that copying something is just imitation. While it might be the highest form of flattery, it’s considered the lowest form of creativity.</p><p>When you ‘steal’, you make an idea your own. You re-interpret, re-invent and transform the idea into something new and improved.</p><p>As product managers, we take inspiration from other products. It’s a smart place to start and allows us to factor in user expectations. For example, drawing from defacto standards for your product can boost adoption by lowering barriers to learn.</p><p>Yet the best product managers don’t stop there. They apply their own iteration and create a unique solution. I remember that it used to upset me when products I had produced were copied by a competitor. Now when I create a solution that serves as a new point of reference for others, I see it as a mark of success. And if a competitor improves on my idea, it inspires me to innovate further.</p><h3><strong>“Art is the elimination of the unnecessary.”</strong></h3><p>Picasso’s lithographs that show the deconstruction of a bull to its most essential lines, are said to be crucial in the secretive training at Apple University. Why? Picasso knew that true art had no place for the superfluous. Real skill lies in simplicity and focus. This is also a vital philosophy for successful product development.</p><p>As a product manager, saying ‘No’ as you execute is critical for success. If you constantly say ‘Yes’, it will no doubt bring about a distracted team and fractured roadmap, possibly resulting in low-value feature bloat in your product.</p><p>Without focus and a clear sense of what’s important, it’s easy to end up with Frankenstein products. Remember that the aim is to delight the customer, not cause confusion or frustration. So simplicity is key.</p><h3><strong>“Action is the foundational key to all success.”</strong></h3><p>Ideas hold so much potential. Yet without action, they become nothing but forgotten dreams. I am a big believer that we learn from our actions and the more we execute, the more successful we become.</p><p>It’s the same for our products. By executing quickly and efficiently, we can treat our actions as learning experiments. Through this iterative and agile approach, we learn more about our customers and the value they see in our products.</p><p>Put simply, shipping new value as often as possible will boost your success.</p><h3><strong>“All children are artists. The problem is how to remain an artist once we grow up.”</strong></h3><p>As children, we have unlimited creativity — whether it’s building a fort or crafting unrestrained artworks. Some of my earliest memories are of that joyful amazing freedom to create. At that age we know no constraints. We only learn to put ourselves in a box as we grow older.</p><p>Although Picasso could paint impeccable realism, he is more well-known for his work that went against conventions. That’s because Picasso’s best work was when he allowed himself to see and express the world without rules.</p><p>Reconnecting with that child-like freedom of thinking is a great way to solve a product design problem. Rather than reaching for the obvious, think outside the box.</p><p>It can be helpful to interrupt your usual neural patterns. Try listening to music that’s the opposite to your usual style and find the joy in it. Take a first-time class that’s out of your comfort zone, such as pottery or martial arts. And ask yourself, ‘If there were no limits or constraints, what solution would I propose?’ You’ll be amazed at the inspiration you could unlock.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DUecuyGtWhamGMCjt3Vl_g.jpeg" /><figcaption><strong>Re-awaken the creativity in your product development</strong></figcaption></figure><p>Innovation knows no bounds. These are just some of Picasso’s quotes that can help re-ignite your own creative spark. So take inspiration from the great masters of the creative arts and infuse these philosophies into your daily practices and principles. After all, how many times have you seen a painting in a museum and thought,<strong><em> ‘I could do that!’</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a13870d96ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you spend enough time with customers? Here's a challenge for you.]]></title>
            <link>https://lyndonmaher.medium.com/do-you-spend-enough-time-with-customers-heres-a-challenge-for-you-389c505b3d81?source=rss-2bc9c2ce19f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/389c505b3d81</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Lyndon Maher]]></dc:creator>
            <pubDate>Fri, 29 Jun 2018 02:31:12 GMT</pubDate>
            <atom:updated>2018-06-29T02:31:12.477Z</atom:updated>
            <content:encoded><![CDATA[<h3>Do you spend enough time with customers? Here’s a challenge for you.</h3><p>Product managers who know me have no doubt heard me say: ‘Don’t be an armchair product manager.’ With so many internal experts and stakeholders in today’s workplaces, it’s an easy trap to plug away in an office without ever speaking to an actual customer. But your colleagues are not surrogates for the end user. And to develop truly successful products that your customers love, you first need to know our customers intimately.</p><h3><strong>Form a partnership with customers</strong></h3><p>Have you ever wondered how so many startups get it so right? It’s not just good luck. The reality is that most startups are incredibly good at being customer-focused. There is no substitute for time with customers, but this is something that bigger corporates and established businesses tend to lose sight of over time. The pitfall is that they end up focusing on things that they assume their customers need or want, and miss the mark when it comes to providing real value to customers.</p><p>The most innovative and effective product managers know that they need a partnership with customers — because when customers are successful, everyone is successful!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rKomyv6EwzCDQ6BExEfP5A.jpeg" /><figcaption>How much time are you spending with your customer?</figcaption></figure><h3><strong>Time with customers delivers real results</strong></h3><p>Throughout my career, one thing has remained the same — I always start with an acute understanding of the customer and industry. In my first week at Domain, I got straight out onto the road to meet real estate agents. And I set an objective for my team to spend an average of 20% of its time each week with customers, ongoing.</p><p>This kind of partnership makes a huge difference. Direct contact with customers helps you understand how they’re using your product, where they see value and what are the sticking points that could be improved.</p><p>While developing a recent app for real estate agents, my team averaged one full day a week talking to customers and observing their behaviour. A key insight was that real estate agents didn’t actually want all of the features of their office CRM in their pocket. This helped us to narrow in on the features that they valued and needed.</p><p>From there we recruited early adopters to give us feedback, so we knew the most important capability to get live first. Not only did we get version one into the App Store more quickly, but it was tailored to what our customers actually wanted from the product.</p><h3><strong>A challenge! Could you be doing more with your customers?</strong></h3><p>Knowing your customers is crucial to being a great product manager. Think of it as one of the four legs on a chair — without that foundation, you’ll fall flat.</p><p>So hold yourself and your team accountable.</p><p>Go back through your calendar and do an honest audit of the hours you spent with customers last month. Use that as your baseline.</p><p>Then I would like to issue a challenge: set yourself a quantifiable and achievable goal of spending more time with customers over the next 90 days.</p><p>Communicate this with your manager, team and customer base. That kind of accountability will give you the extra drive to really make it happen. And the chances are that you’ll uncover some really useful insights!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*JeuhAtL3fuk-BaTBNd5YyA.png" /><figcaption>Tip: It is super easy to setup a customer calendar in Google Calendar (this is what I do), you can then share this calendar (not your entire calendar) with your team, boss, sale team etc. — holds you accountable, communicates who your meeting with, and is easy to visually track your customer time at a glance…</figcaption></figure><p>Good luck …</p><p>Follow me on twitter: <a href="https://twitter.com/lyndon_maher">https://twitter.com/lyndon_maher</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=389c505b3d81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Kevin Rose's innovative BETA program approach can benefit your work]]></title>
            <link>https://lyndonmaher.medium.com/how-kevin-roses-innovative-beta-program-approach-can-benefit-your-work-fe56c8f47ed5?source=rss-2bc9c2ce19f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe56c8f47ed5</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Lyndon Maher]]></dc:creator>
            <pubDate>Mon, 11 Jun 2018 03:05:56 GMT</pubDate>
            <atom:updated>2018-06-11T03:05:56.209Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How Kevin Rose’s innovative BETA program approach can benefit your work</strong></h3><p>Long before we were looking to Facebook or Twitter for the latest news content, there was Digg.com. As a social platform, it pioneered the way. And its founder, <a href="https://twitter.com/kevinrose"><strong>Kevin Rose</strong></a>, continues to be a leading innovator in software product development.</p><p>I’ve been following Kevin’s work for almost two decades now. Since Digg.com he has launched a string of successful products and is now a venture capitalist at True Ventures. He consistently contributes to the industry and I took away a lot from his <a href="https://www.youtube.com/playlist?list=PL6bwBOy2Mzf5FqU1S2s_Y6dIC3zhcH2yk">Foundation video series</a>, where he interviewed over 40 tech entrepreneurs from 2010 to 2015.</p><p>You can imagine my reaction when in 2017, Kevin announced that he was going to make the entire product development process of his new app public. What an opportunity!</p><p>As a product guy with ample experience taking apps from idea to launch and beyond, I wasted no time requesting to join Kevin’s closed Facebook group. And I was in good company with 17,000 other professionals.</p><p>The nine months leading up to the release of ‘Oak Meditation’ to the iOS App Store was essentially a masterclass for those building new products from scratch.</p><h3><strong>Here are some of the key insights that you could apply</strong></h3><p><strong>1: Facebook is a great free platform for running a BETA program</strong></p><p>It probably isn’t the first platform to come to mind, but a Facebook group is a surprisingly effective way to run a BETA program. After seeing how Kevin did this, it will definitely be part of my toolkit in the future.</p><p>This is why it works so well:</p><ul><li>Facebook live videos are the perfect way to provide regular engaging demos of your app updates and get feedback at scale via the comments.</li><li>Photos can be uploaded and the commenting and likes features used to capture early feedback on new screen layouts, and so on.</li><li>Facebook polls are a great way to gather votes to help you make key decisions.</li><li>The news feed and push notifications keep your community up to date via a social app they’re already actively using.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQGurW8mXuYwU22sGubxiA.jpeg" /><figcaption>Try using Facebook for your product’s next BETA program</figcaption></figure><p><strong>2: Virtualise the discovery and research process, cheaply</strong></p><p>With such national and global set ups these days, scheduling interviews and feedback sessions can be a bit of a headache. Utilising a virtual approach for your discovery and research process saves a lot of time and money — which is a win in any terms!</p><p>Here are some pointers I learned from Kevin’s approach:</p><ul><li>Conduct research at scale with Facebook as a launch pad and tools like google forms and type-form surveys.</li><li>Get faster feedback using Facebook by uploading screen recordings of your app rather than conducting in-person demos — the iOS 11 screen capture update has made it even easier.</li><li>Explore your options. I’ve previously used <a href="http://intercom.com/">Intercom</a> while in BETA mode. It can provide a quick in-app way to conduct research with active users of your product. And if your user base is small, the messages plan is cost-effective for up to 250 users.</li><li>Leverage your following. Kevin has such a strong personal brand that he exceeded the number of users Apple allows for its BETA testing platform ‘TestFlight’. Even if you don’t have a huge network, a virtual approach will still help you to conduct quick research from 10 to 100 early BETA users.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z1-DaD3svg2s2QMZqeMhYQ.png" /><figcaption>Use tools that help you communicate visual and engaging updates.</figcaption></figure><p><strong>3: Choose progress over perfection with an earlier BETA release</strong></p><p>Let’s be honest — no matter where you’re at in your career, the idea of sharing your unfinished work can be the stuff nightmares are made of. But don’t let perfection get in the way of progress. The last thing you want is to be finding issues in the general release!</p><p>Releasing your BETA as early as possible gives you valuable feedback on what is already operational. Most importantly, it can help you validate or better understand key assumptions and hypotheses.</p><p>Kevin’s first BETA was rough. Yet it was enough to get early valuable feedback on components of the core meditation flow. This was quickly incorporated into improvements in subsequent BETA updates.</p><p><strong>4: Naming doesn’t have to be (quite so) hard</strong></p><p>Gems like Strava and Twitter don’t just fall from the sky. I have to admit that I’ve never found it easy to come up with a stellar name for a new product. So it was great to see that Kevin also found this to be “the hardest part of the entire process”.</p><p>These are some useful tips I picked up from Kevin’s approach:</p><ul><li>Use your early BETA group community to collect suggestions, because great ideas can come from anywhere and anyone.</li><li>Find out what resonates with people through an online survey.</li><li>Make sure your name passes the “bar test”. Say you were in a bar and told someone what you were working on, then the name. If they were to ask you to spell or repeat it — that’s a fail. Your name needs to be clear, memorable and spelt as it sounds.</li><li>Look at <a href="https://en.wikipedia.org/wiki/List_of_Apple_codenames">Apple code names</a> and <a href="https://en.wikipedia.org/wiki/List_of_Microsoft_codenames">Microsoft code names</a> for inspiration. This is just the sort of cool and unique thinking that can spark new ideas, and I’ve now bookmarked the pages!</li></ul><p><strong>5: Convert your BETA users into ambassadors</strong></p><p>If you’re like me, you’ve seen that those who have been involved in the development of a product are more invested in it. So converting your BETA users is a bit of a golden egg. The chances are that they will be avid users who passionately promote the app to their own networks. Could there be any more convincing advocates?</p><p>Kevin did this perfectly. Upon launch, he thanked the community and invited members to be first-time users. You can imagine how many immediate downloads that resulted in! And ideally, this would lead to 5-star app ratings.</p><blockquote>A big thank you to our 17,000+ community of testers. Without your surveys, comments, and emails, we couldn’t have built this app. Kevin Rose</blockquote><p>The other upside is that you’ll have a few friendly customers on hand who could provide testimonials for PR around the launch.</p><p><a href="https://medium.com/@kevinrose/oak-meditation-f8478d9fc00">Introducing: Oak</a></p><p><strong>6: Creating mood boards helps with briefing designers</strong></p><p>When you’re not experienced at briefing designers, it can be hard to get your vision across. Of course, the essentials include outlining customer problems and the product objectives, as well as how you will measure success. But designers are visual people.</p><p>Kevin demonstrated an effective way to convey expectations around the general mood, look and feel. He found designs on Dribble and created a Pinterest board to share with the designer. This is a quick way to get everyone on the same page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhUUSPqf_4kTqdhS7JY9kA.png" /><figcaption>Create a mood board on Pinterest to help when briefing your designer</figcaption></figure><p><strong>And an exciting update from Kevin…</strong></p><p>On 26 May 2018, Kevin shared with the Facebook group that after almost seven months of Oak Version 1 being live, Oak Version 2 was being released to the BETA Group.</p><h3>Kevin Rose ⛩ on Twitter</h3><p>Here is a sneak peek of Oak v2.0 :) https://t.co/LWbtM8R2yf</p><p>I loved his <a href="https://www.useloom.com/share/3d10927022d84094a621fafb7828646e"><strong>video update</strong></a> and it was great to see some of the enhancements.</p><p>I also learned about two cool new tools from the video:</p><ol><li>Free software which is a Google Chrome browser plugin — “<a href="http://useloom.com/">Loom</a>” to record video updates with screen share.</li><li>A browser-based design tool, called <a href="https://www.figma.com/">Figma</a> It’s an interesting-looking alternative to “Sketch” and I’ve already started playing around with it.</li></ol><p><strong>Importantly — transparency leads to better apps all around</strong></p><p>These are just a few of the gems that Kevin shared. Some were already in my playbook and others were new. Either way, it’s a fresh and transparent approach that I’ll definitely be rolling out in the future.</p><p>Personally, I would love to see more companies take this type of ‘behind the curtain’ approach to product development. It’s one hell of a contribution to the industry and other app developers going through the same process. It’s also reassuring to see that those we admire face the same challenges we do. For instance, Kevin lost his only iOS developer — to Apple, no less. Losing great engineers is something we all face as entrepreneurs and product leaders.</p><p>With this kind of transparency ongoing, think of what we could achieve? It’s a great way to pay it forward to the product and start-up community and will ultimately result in better apps all around. That’s a win-win if ever there was one.</p><p><strong>Links:</strong></p><p><a href="http://www.oakmeditation.com/"><strong>http://www.oakmeditation.com</strong></a></p><p><a href="https://twitter.com/kevinrose"><strong>https://twitter.com/kevinrose</strong></a></p><p><a href="https://www.kevinrose.com/"><strong>https://www.kevinrose.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe56c8f47ed5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What you should consider when choosing to work for a startup or a corporation]]></title>
            <link>https://lyndonmaher.medium.com/what-you-should-consider-when-choosing-to-work-for-a-startup-or-a-corporation-2bd6fda37526?source=rss-2bc9c2ce19f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bd6fda37526</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[intrapreneurship]]></category>
            <category><![CDATA[recruitment]]></category>
            <dc:creator><![CDATA[Lyndon Maher]]></dc:creator>
            <pubDate>Mon, 11 Jun 2018 02:44:47 GMT</pubDate>
            <atom:updated>2018-06-11T02:45:16.627Z</atom:updated>
            <content:encoded><![CDATA[<p><em>………originally published March 2016</em></p><p>You’ve heard the stories about what it’s like to work in a startup. They’re usually fast-paced, feature daily beer sessions, endless games of ping pong and free snacks. There’s often a younger crowd, and a real sense of camaraderie — a “we’re taking on the world” type mentality.</p><p>Despite these perks, it also means you’re typically working with a much leaner team and limited resources.</p><p>While many skilled technology professionals in Australia are jumping ship from the corporate world to startup land, I bucked that trend. Having gone from one of Australia’s most successful startups, Bigcommerce, into a big corporate digital enterprise, I have a unique perspective on what to look out for in a corporate environment to ensure you don’t lose that “edge” that’s so enjoyable in a startup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y2peHlDo58htIHY2" /><figcaption>Photo by <a href="https://unsplash.com/@headwayio?utm_source=medium&amp;utm_medium=referral">Headway</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Here are the five qualities I learnt from working in a startup, so you know what to look out for, ask about in interviews, and talk to other employees about before taking a role in a corporate technology or product team.</p><h3>1. Approach to customers</h3><p>Startups are extremely good at obsessing over their customers, for good reason. In the early stages of a business, every customer is critical to success. Many corporates, who already have big customer bases, forget to do this. If you want to find out if a corporate is customer-centric, try their products. Contact their customer service. Try to navigate their website as if you were their customer. If it doesn’t hit the mark, make sure you discuss what their customer roadmap is.</p><h3>2. Access to senior executives</h3><p>In a startup environment, founders are typically much more involved in the day-to-day operations of the business. It’s highly likely the CEO or founder will be present at more meetings and be actually working alongside you. This presents a great opportunity for you to learn from them, as well as have greater insights into the wider direction of the business, its vision and strategy. It’s still possible to have this within a corporate, but you should always try to get an indication in the hiring process how flat a structure is. Take note of who is interviewing you, ask to meet with team leaders, and talk to other employees if you can.</p><h3>3. The “always pitching” state of mind</h3><p>In my experience working at a startup, you’ll likely find yourself in what we call an “always pitching” frame of mind. Co-founders are always pitching their business to customers, investors — anyone who will listen, and more often than not, they expect the same from their employees. It’s critical to look for this passion within a corporate environment. Is there excitement about what the company is doing? Is there momentum? Read the media, read customer reviews and even HR websites like Glassdoor. A good corporate will foster this excitement in its employees. If senior leaders are excited, employees generally will be too.</p><h3>4. Problem solving</h3><p>Working in a startup teaches you to work hard, on lean resources, under pressure — which can be an extremely valuable skills regardless of the working environment. You’ll likely be given more responsibility and more autonomy, given the size of the team, but this will mean you’ll be able to expand your skill set and widen your approach to problem solving. There’s more of a “think on your feet”, “try and test” type mentality to solving problems in a startup, which can be extremely valuable in the long run. A lot of corporates talk about being “agile”, but make sure you ask about how teams work, and for concrete examples of agile practices. Plenty of corporates are establishing “startup in a corporate” teams, being led by managers and leaders who have grown up in startups. Always look into the employment history of those you’ll be led by.</p><h3>5. Technology behind the business</h3><p>One last thing you should always consider is the technology powering the business. Typically in a startup environment the founder may have built the technology stack in a very lean, bootstrapped way. And while it’s clear why a startup would approach technology in this way, it can also mean you may have problems when you go to scale the business. It’s really important to know what you will be working with. And this applies to any business — startup or corporate. Understanding the technology stack you have at your disposal can largely impact your ability to work, so it’s an important factor to consider.</p><p>Startups are incredible, challenging, exciting places to work. But at the end of the day, beer, ping pong and a snack cupboard are just icing on the cake. Don’t be fooled by the clichés when considering whether to choose a startup over a corporate — — you might be surprised if you can dig underneath the hype.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bd6fda37526" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>