post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

How to build a companion product and win user trust

mission statement

Deep dive: Crafting your product vision and mission

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

How Google makes AI work at Enterprise scale – Miku Jha (Director, AI/ML and Generative AI, Google Cloud)

5 ways to invent and simplify as an AI/ML product manager

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

Building your own user experience and software stack: This week’s product news

With a career founded in writing, I pivoted to Product, enjoying the challenges offered by managing diverse products while bringing clarity of communication to my work. I&#39;m passionate about seeing how fast the space is evolving, and always interested to be part of the conversation, whether as a contributor, or writer.

Head of Product

Jon Horvath

In his opening keynote session at #mtpcon SF+Americas 2022 day two, <a href="https://twitter.com/ojiudezue">Oji Udezue</a>, Product Lead at Twitter, examines the key elements needed to create impactful product systems that elevate everyone.
Watch this video or read on for key highlights from the talk.
<ul>
<li>Good product system results in better business outcomes</li>
<li>Prioritising people means investing in talent &#8211; from hiring, to progression, to promotion</li>
<li>Invest in execution to deliver faster, clearer, continuous value</li>
</ul>
Oji describes the ideal product system as one which is explicit, responsive and malleable, and ‘allows us to create great products on autopilot’, delivering reliable hitmakers. It should support scaling and maximise output, while minimising the rate of errors. Oji introduces 3 elements of good product systems:
<h2>Systems with people</h2>
‘Talent is the coin of the realm’ Oji says, describing how ‘it&#8217;s the people that build good products’. A good people system, he explains, is on one side about ‘identifying great talent to join your organisation’ and on the other ‘getting the last ounce of ingenuity from highly motivated people in your organisation’. He outlines 3 main considerations of people systems design:
Organisational design: While there’s no single standard for organisational design, Oji recommends using a militaristic framework to ‘design for the mission you have and not the mission you don&#8217;t’. He suggests sketching several plans, listing the pros and cons of each before adopting the best parts, and then continually optimising, so you ‘never get stuck in an immovable design [&#8230;] react to a changing mission.’
Assessing and assigning talent: A ‘clear career competence ladder’ is critical, Oji says, explaining the need to define the skills and competences your organisation requires for every role, and aligning processes of ‘hiring, to promotion, to assessment’ around those individual competences.
Coaching, performance and reward culture: ‘Nurture and evaluate’ talent, while embedding practices of reward-giving into company processes, and connect kudos to performance reviews, progression and promotions. On coaching, Oji says ‘everybody should coach’, recommending teams look at distributing the pressure of mentorship across the organisation, with new starters supported by mid-level employees, and mid-level employees supported by seniors, supporting growth at all levels.
<h2>Systems of direction setting and strategy</h2>
Oji explains the importance of setting a direction that is clear, easy to align to and customer-focussed. He outlines 2 things to consider when constructing a system of direction setting:
Direction setting at rest: For already established systems, Oji describes ‘setting at rest’ referring to cases where a system can be defined, documented and shared across the organisation. Looking inwards can be a practice of aligning on the fundamental customer problem the business is trying to address, and then positioning the strategy toward a Northstar KPI. The outward view is ‘to maintain an ongoing synthesis of the market’ and understand what changes are approaching and, when change comes, what the impact will be. Oji advises that we articulate and re-articulate strategy using a 1-pager, recommending ‘VMSOP; which means Vision, Mission, Strategy, Objectives, and Priorities’.
Direction setting in motion: Setting direction in motion means comparing your ‘shared reference’ (the document described in the system at rest), to ‘a current synthesis of the market, and figuring out if you can do the things you need to add to it’. He advises teams to take time weighing up strategic options, looking at breaking problems or evolutions down into different elements, before coming to a synthesised strategy. Once finalised, your updated strategy should be shared across the company to ensure alignment.
<h2>Systems of execution</h2>
Oji outlines 3 things to consider when constructing a system of execution &#8211; something which  allows teams to continually deliver value and avoid ‘stagnation and stasis’.
Resource allocation Oji describes resource allocation as ‘portfolio theory’, the process of understanding the cost of investing in each bet by looking at the allocation of people and talent, and comparing it to the importance of the change, and likelihood of success. Oji encourages teams to minimising dependencies, as they lead to uncertainty which can increase the cost of resourcing, making execution harder and less likely to succeed.
Playbooks: While most of us recognise the importance of documenting processes or key concepts like ‘customer listening, discovery, experimentation, data analysis, opportunity assessments’, Oji explains that to have a product system focussing on execution, you need to ‘find the key things that people need to do to innovate and try to write a playbook’. This document defines what the essential steps are to innovate, and what the key rituals teams need to follow. Oji refers to a section of a playbook written at Twitter that ‘allowed people to get stuff into production very quickly, once they got into the company’. He describes how these are working documents, ‘you play, try to standardise them; make them clear so that people can make them consistent all the time’.
Alignment: Understanding whether teams are aligned can be as simple as asking people to fill out a Google Form, Oji says, examining how alignment is something that should be practised intentionally, and systematised to achieve desired outcomes. He points to decisions and handoffs between teams as areas which need particular focus, as ‘sometimes there&#8217;s limbo [and] people don&#8217;t really realise what hard decisions are made’.
Oji ends by describing how ‘the best companies will create a product system to elevate everybody’, he says, ‘people should have the right to upgrade it [&#8230;] you make space for yourself when you improve the product system in a visible way &#8211; make it more explicit.&#8217;
<h2>There&#8217;s more where that came from!</h2>
Explore more #mtpcon SF+Americas 2022 <a href="https://www.mindtheproduct.com/mtpcon-sf-video-library-2022/" target="_blank" rel="noopener">video content</a> or use our <a href="https://www.mindtheproduct.com/content-a-z/">Content A-Z</a> to find even more product management insights.

core/freeform

What good product design looks like – Miguel Fernandez (VP of Product Design, Slack)

Product Systems: How to manufacture lightning in a bottle by Oji Udezue

Jon Horvath