Updated 2 months ago
I didn’t want to write a verbose blog post about the past year but the more I got to thinking, the more I felt it necessary to document (mostly for myself) the key lessons I’ve learned from this past year. These lessons are not necessarily about Covid, they’re about other factors that have impacted on my life too such as losing my father and from what my latest startup adventure has taught me.
Below are my observations, maybe you’ll be able to learn something from these too.
This might feel obvious with a cursory glance, but it’s true. Lots of people say it, and lots of people have varying opinions on what ‘learning to build your idea’ truly is. In my mind, it’s whatever it takes to realise your vision enough to make sense of it as a true end product, even if that’s incredibly MVP.
I took this approach by building out Figma plugins to scratch an itch around weird interface quirks or missing features. I could have not bothered, or I could have asked someone else to build it, or even find the nearest alternative. But the reality is, I spent the time to learn to create them myself, in turn, I better understood how Figma works under the hood, and finally learned lots of valuable TypeScript along the way.
It taught me a lot about shipping products to customers, whether it’s free or not, it matters. And it taught me a lot about taking on feedback and improving ideas, but without just doing everything someone asks for.
Pithy takeaway: Learn to build things, no matter how small.
Design systems are complicated, they’re time consuming to build well and there’s still an enormous gap between the designed design system (in Figma, Sketch or another tool of choice) versus the coded component library (the name difference alone is irritating!).
However, taking the time to build out a robust system makes the world of difference in the long run. If you take the time to create flexible components, and think about their relationship to each other and their scalability, you’ll start to reap the rewards pretty fast. If you can keep lesson 1 in mind too and actually try to create any of these in Vue, React, Swift or similar, then you’ll also find limitations that allow you to rethink how you designed it in the first place. So you can go back and improve on its flexibility and scalability.
Robust systems also ensure consistency of your brand application across interfaces and other media. I saw a lot of worry previously about design systems being so good that a developer can build content without a design. Great! That should be the goal. If they can build views without Design mocking them up, Design can focus on defining the intention of the work, it’s reason for being, the customer value, the stakeholder needs etc. Designing the intention, not designing the mock.
Pithy takeaway: Design systems create room for more intentional work.
Learning how components are built, giving it a go yourself, that’s all useful in ensuring a positive handover experience with Development/Engineering. But if they’re not onboard with the design strategy and don’t buy in to the use case of components then you’re never going to build the best bond for the best end product.
Designers and Developers should be like Ham and Cheese, no matter what they go together. You should be in each other’s pockets in a positive way, defining and scoping solutions from the outset, together. If you show willing by trying to prototype a component in real code or just showing that you’ve considered limitations though good documentation, it’ll go a long way. A great engineer will take the time to explain other limitations you may have missed and together you’ll build something truly scalable and great.
Pithy takeaway: Start building that relationship as early as you can. It makes the world of difference.
Businesses have needs that can often vary from what the product really requires, for example, when fundraising a business will be focused on optics and future product vision, whereas during a period after fundraising, they’ll likely focus more on growth.
It’s common for these business needs to clash with product needs. Often VCs will turn down businesses by not ever saying no, and instead, by offering product feedback so they keep an open door in case you suddenly do find the traction they desire. When they do this, it’s easy for stakeholders outside of the Product team to prioritise these seemingly “important” features. The reality is, these features are merely an easy out for the investor and will often lead to feature bloat in your product.
It’s a tough line to walk, trying to appease VCs or business stakeholders is important, but it can be super hard to do this without straying from your product roadmap.
Pithy takeaway: Compromise is key, but don’t let business requirements derail your product roadmap.
Never underestimate the power of building strong relationships. Working at startups, or any company for that matter, is incredibly difficult. But in reality, it’s just business and businesses have their ups and downs. What gets you through is having strong relationships. Focus on building them and harnessing them to air out your concerns and worries along the way.
Having great friends outside of work is awesome, but they don’t know what the day to day feels like. Having great colleagues internally, makes all of the difference. They understand the nuances of the businesses and are often times going through what you are. Don’t be afraid to be vulnerable but avoid falling into hearsay and negativity.
Pithy takeaway: Great relationships at work will see you through the toughest times.
A good Product Manager (PM) is like a good red wine; let them breathe for a little while and they’ll only get better. I’ve seen situations where Product Managers are essentially just task managers, writing Jira tickets and little more. This isn’t good product management or good use of a Product Manager. They should write Jira tickets for definite, but not just that.
A good PM is given the freedom to do what they need to do at any time. To drive the team forwards and push for the best outcome for both the business and product team too. A good PM also works closely with design at the outset, working through user experience documentation and process; helping to define the pain points and intended happy paths, being part of the user research process, supporting the design documentation process and ensuring that there’s a solid brief.
In some ways, in the outset of the design process, it should be hard to know which person is the designer and which is the PM, only when it comes to pursuing wireframes and detailed design processes should that split occur.
Pithy takeaway: Product Managers are essential, but give them room to do their job!
This is a personal one, but maybe one that is good to share. I’ve learnt that caring about both design and development, understanding both of those processes and being confident in both are what excites me and keeps me motivated. Knowing that, writing it down and owning it, helps me to stay on course with my passions and guides my life choices accordingly.
Pithy takeaway: Find your perfect fit. Lean into it. And never let it go.
Like a Monopoly ‘Chance’ card, taking a chance can be a risk that either has a reward or a negative consequence. Either way, every chance you take is a lesson learnt and in many ways is a chance to grow and evolve. Chances can either validate your decision making and improve your life or invalidate your decision making, change things and cause you to course correct. No matter which it is, you learn a lot by taking them.
Not all chances are created equal though. Gambling is chance (unless you’ve got some mad skills) and is more often than not, likely to end badly. Changing careers is a chance that can equally either pay off or lead to a need to flip again. But whatever happens, own the chances you take and look at them from a longer-term perspective. You might find that what once felt like the worst thing that could ever happen, actually ended up changing your life for the better.
Pithy takeaway: Over the long term, chances are what teach you the most.
Those who are close to me will know that I recently lost my father to his battle with cancer. It’s been a very tough couple of months but practicing elements of buddhist and stoic ideologies has helped me to work through it all. Equally, channelling my inner “Dad” has helped a lot too.
My Dad was a true stoic, minimalist and intentional human. He believed in living in the present moment always and through his diagnosis and 6 and a half years of dealing with it, he never once complained or let it hold him back. Instead he made the most of every single moment he had on this planet. He explored parts of the country he’d never seen before, spent time with the people he loved most, focused on restoring a forest nearby to where he lived and gave back to the planet more than he ever had before.
I’m now focused on channelling him as much as I can to live my life with the most intention.
Pithy takeaway: Live every moment with intention, but not like it’s your last.
We’ve been through a lot as a planet lately, but it’s still very easy to live in a bubble of your own individual life and community (online or offline) without really appreciating what you have.
I’ll keep this one short and sweet. But now more than ever, I have nothing but gratitude for my life, my family, my friends, and my career.
Pithy takeaway: Love what and who you have in your life.
This site, and all of my work, is dedicated to my hero, my inspiration, and the strongest man I've ever known. My father. I love you Dad ❤️.