Proof of Concept - Managing towards outcomes
Outcome: A final product or end results. “Manage towards outcomes,” a VP of Engineering I worked with always says. It’s something the EPD group I worked with would keep as a mantra. This framing, while tiny in detail, is crucial to remember in the midst of the chaos of work. As a manager, you want to avoid the resource management trap—thinking about how time is used vs. what needs to get done. This applies to both overseeing your team and how you as a manager prioritized your own time. Many people’s first role as a manager starts with direct line management—overseeing a specific team with no layers. It’s natural for line managers to think about resource management. That was the intention of the role of managers overseeing people in an assembly line—less relevant in building a tech company. Managing towards outcomes is focusing on the intended results and affecting change towards that. This sounds obvious, but is easier said than done. Instead of thinking about the time needed to achieve a result, focus on what needs to get done and the inputs required to achieve it. As important as being people-centric as a leader is, you are a leader of the outcome. A Head of Product is responsible for the outcomes of the product, not only the people on their team doing the work. There are other factors such as operations on how the work is delivered, the quality of the work, and balancing financial resources in order to achieve it. The input/output exerciseWhen forced with complex challenges, I try to distill it to the simplest form of it. The input/output exercise can help you map what you need and are doing to the desired outcome. This exercise has three components:
OutcomesThough it’s out of order from left-to-right, start in the center with the desired outcome. Reflect on your team’s purpose and how they contribute to the company vision. How you determine the desired outcome varies on the maturity of your company. If you’re at an earlier stage company, you may not have any benchmarks to move any metrics. It’s better to have a task-oriented desired outcome that’s clear than realize a metric you set can’t be measured. Keep in mind the following are important factors but not outcomes: effort, process, motion, status, and intent. InputsInputs are what your team needs in order to achieve the desired outcome. This may be resources needed, information, or something unblocked in order for your team to do their work. A few examples of inputs are: data, headcount, dependencies with other teams, etc. OutputsWhat is delivered to inform the outcome. The outputs are artifacts—proof of work what your team made happen independently of the inputs. The outputs either directly contribute to the outcome such as a product shipped or go-to-market campaign launched. However, they can also be artifacts that inform a desired outcome. For example, a research team’s value is not building and shipping the product but deliver an artifact of insights that inform what is built. The outcome of outputs vary on timeline. Because designs are delivered recently for a new feature doesn’t mean ARR will skyrocket. However, it may be the blueprint of a missing customer need that results in it down the road. Here’s what a recap of your input/output exercise might look like::
How you spend your time depends on the desired outcomeI describe management in three core aspects: operator, strategist, and coach. It’s not a perfect distribution across everything you do. Where you prioritize your involvement varies on each direct report, priority, and how things are progressing. It’s not set it and forget it. It’s being constantly heads up over heads down. One of my favorite frameworks is Hersey-Blanchard’s Situation Leadership. It’s a great exercise to help you think about how you prioritize your involvement across the team. Depending on the desired outcome and how it’s staffed, you may be hands on or hands off. There are areas of responsibility where there might be more maturity that you can be hands off. While you’ve delegated that area, there might be a new team you’re building that requires you to initialize the work as you hire the team. This is my recommendation on how you balance your time—allocation based on every work stream vs. a catch-all across the entire organization. Outcomes evolve—iterate
Managing towards outcomes will need to be balanced with reality. Don't be surprised that once you set desired outcomes with lovely inputs/outputs that things change. This happens frequently in organizations with rapid change. The speed in moving to a different direction is crucial to stay alive—the difference between navigating a speedboat vs. turning an aircraft carrier around. A former manager once told me you have to choose which fires requires your attention most because there will be multiple fires. Rebalance your focal area weekly, if not daily. Managing towards outcomes is difficult to prioritize and think about. It’s why many companies don’t do it. As you fight the fires, stay focused on the desired outcomes—something you should be able to fit on an index card and repeatedly articulate. Avoid the resource management trap and manage towards outcomes. Hype links
Job opportunities
1 This is not the monolith I was expecting to return after the pandemic You're currently a free subscriber to Proof of Concept. For the full experience, upgrade your subscription. |
Older messages
IDDE: The infusion of design and dev tools
Sunday, March 31, 2024
Issue 188: It's time to kill design handoff and create software differently ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
The oil and water problem
Sunday, March 24, 2024
Issue 187: Old and new guards at startups ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
The minestrone of talent
Monday, March 18, 2024
Issue 186: Join startups where there is high density of talent ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
The soul of your work
Sunday, March 10, 2024
Issue 185: The importance of the maker's devotion ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Design Engineering
Sunday, March 3, 2024
Issue 184: An emerging role in software ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
You Might Also Like
Accessibility Weekly #419: Understanding VPATs and ACRs
Monday, October 21, 2024
October 21, 2024 • Issue #419 View this issue online or browse the full issue archive. Featured: Understanding VPATs and ACRs: Key insights "This week I had a bunch of requests from clients
Mentorship
Sunday, October 20, 2024
Issue 217: Thoughts on the most important relationship in your craft ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Halloween Email Templates & Newsletter Ideas
Sunday, October 20, 2024
This week, we've released a selection of new Halloween email templates, ready for you to use directly from your Designmodo account.͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Driving stick shift
Sunday, October 20, 2024
Issue 216: The importance of manual driving in a world of copilots ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Accessibility Weekly #418: When Team Opinions Differ
Sunday, October 20, 2024
October 14, 2024 • Issue #418 View this issue online or browse the full issue archive. Featured: A11y at work: When team opinions differ "Sometimes working with a larger team means that you'll
#478: Inclusive Design
Sunday, October 20, 2024
Accessible numbers, ADHD, readability guidelines, neurodiversity design system and inclusive mindset workbook. Issue #478 • Oct 15, 2024 • View in the browser Smashing Newsletter Hej Smashing Friends,
Inside Mark D. Sikes’s Historic Renovation of Blair House
Sunday, October 20, 2024
View in your browser | Update your preferences ADPro Design Within Reach Turned a San Francisco Warehouse Into a Certified-Cool Flagship—And AD PRO Directory Members Got a First Look Inside On
Oops! Here's the Correct Edition of The Source
Sunday, October 20, 2024
View in your browser | Update your preferences ADPro Revisiting AD's Coverage of a Presidential Dwelling We accidentally sent out today's newsletter with the wrong text, here's the correct
12 real life business transformations, plus what are you reading?
Sunday, October 20, 2024
Learn how to make your business grow and glow! ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
How to Boost Your Profile, According to Kelly Wearstler and More
Sunday, October 20, 2024
View in your browser | Update your preferences ADPro Everyone's an Influencer Of course there's beauty in privacy—but for business owners, building and maintaining a public profile is essential