Michael Rill

Einfach machen

Category: Leadership

  • The pivot fallacy

    The Reckoning

    It was  5:47pm on a Friday after a long week of work. Only the quarterly business review separated the team from a well-deserved weekend. Routine. But this one felt like a reckoning. The product team sat in uncomfortable silence as the VP of Product sketched bold new goals on the whiteboard. These weren’t the goals they’d been working toward. In fact, no one was entirely sure what had happened to the goals they had been working on.

    “This is what we need to do!” the VP declared, underlining the new vision with a flourish.

    After a long stretch of silence someone finally spoke up: “What about the initiatives we kicked off last quarter? Are they still a priority?”

    The VP frowned, already erasing a corner of the whiteboard. “We’ve pivoted since then. This direction is more aligned with our growth strategy.”

    The word “pivoted” hung in the air – again. Frustration simmered around the table. The engineers felt whiplash. The designers were demoralized. The product managers were overwhelmed. No one could deny the ambition in the VP’s vision, but they’d seen this play out before: a flurry of excitement, half-finished work, too many fragmented commitments and no measurable outcomes. Nobody could remember the last time they delivered something great they were truly proud of. 

    This time, though, one product manager decided to take a different approach.

    The Turning Point

    After the meeting, she stayed late at her desk, sifting through notes from the past few months. It wasn’t pretty. Goals had shifted. Timelines had slipped. Decisions were scattered across various messaging threads and impromptu hallway conversations.

    “If we keep running like this,” she thought, “we’re never going to get anywhere.”

    So, she did what no one else had done: she started documenting.

    She wrote a clear product plan—not just what the team was doing, but why it mattered. She outlined the objectives, the customer needs, and the measurable outcomes they aimed to deliver. She created a timeline, linked dependencies, and included a section for open questions.

    The next day, she shared it with the team.

    “This is what we’ve been working toward,” she said, “and this is how we’re tracking against it. If leadership wants us to pivot, we need to capture that too—but let’s make sure we’re not losing sight of our progress along the way.”

    The team was skeptical. Documentation felt like just another chore. But as the weeks passed, something remarkable happened.

    The Moment of Truth

    When leadership called another meeting to discuss new priorities, the product manager brought the document.

    “We hear where you’re coming from,” she said, “but here’s what we’re working on right now, and here’s how far along we are.”

    She walked them through the plan: the problem it solved, the expected impact, and the remaining steps. Leadership paused. The VP nodded. “You’re right,” he said. “Let’s get this across the finish line first.”

    For the first time in months, the team felt clarity.

    The document became their compass, keeping everyone aligned and focused. When new ideas surfaced, they weren’t dismissed—they were documented, reviewed, and prioritized against the existing plan. Everyone understood not just what they were working on but why.

    Momentum built. The team started hitting milestones. And when they shipped the product, it wasn’t just functional—it was impactful, solving a real problem for customers.

    The Power of the Written Word

    Without written plans, leadership fills the void with ideas—often brilliant, but chaotic and ever-changing. Documentation doesn’t kill ambition – it harnesses it. It captures the need for explicit structure to create a more inclusive environment, where the new starter has the same access to information as the “old guard”. 

    A well-written product plan provides a foundation for creativity and execution. It turns a team from reactive to proactive, from scattered to strategic.

    It creates clarity in the chaos, showing leadership where progress is happening and enabling teams to balance focus with flexibility. It turns pivots into informed decisions instead of knee-jerk reactions.

    In the absence of a compass, people wander. But with a product plan in hand, teams don’t just execute better—they aim higher and get there faster.

  • Rituals of modern product teams

    In case your podcast queue is running low, I highly recommend queuing up this presentation from Figma’s Config 2023 conference: Rituals of modern product teams – Yuhki Yamashita, Shishir Mehrotra (Config 2023) – YouTube

    The basic premise is that effective teams have established a number of rituals over time, and Yamashita and Mehrotra give a quick rundown of some of those rituals (screenshot below). I am fascinated by the organizing framework they use to categorize those rituals: Cadence, Catalyst, Context. Teams should make sure they have the right mix within their meetings (or updates – not everything has to be a meeting) and not confuse one with the others.

    Anyway, I highly recommend listening to (or watching) that talk.  

  • Getting things done

    More than twenty years ago a book came out by David Allen called Getting Things Done. For a while it garnered quite a cult following and it resonated with me as well. The framework was accessible as it had lots of helpful. tactical advice that was easy to implement, but it also had a lot of depth. Similar to the old PacMan arcade game: “A minute to learn, a lifetime to master”.

    Recently it re-entered my consciousness as the Get Things Done concept popped up twice in short succession, both times taking it literally and turning it into meaningful career advice. First, Andrew Bozworth wrote about it on his blog:

    Too often I see someone who is responsible for accomplishing an important goal doing the best they can in the face of immense odds. It may sound counterintuitive, but the mandate of such a job is not to “do the best you can.” It is to get it done. And if the way to get it done is to ask for help, then that’s what you should do.

    Boz.com – Get It Done

    Then President Obama put it in similar terms:

    I’ve seen at every level people who are very good at describing problems, people who are very sophisticated in explaining why something went wrong or why something can’t get fixed, but what I’m always looking for is, no matter how small the problem or how big it is, somebody who says, ‘Let me take care of that.’ If you project an attitude of, whatever it is that’s needed, I can handle it and I can do it, then whoever is running that organization will notice. I promise.

    Barack Obama’s career advice

    Both times, the concept is so simple, that I feel a bit awkward turning those three words into paragraphs. Similar to PacMan this is easy to learn, but will be meaningful on every level throughout your career: Move something that is not “done” yet and get it into a state that is considered as done. No matter how small or big this is.

    Over the course of your career, the “Things” part will likely increase in scope as you gain more expertise and competence. And the tactics you have to employ to get them to “Done” will be likely change from individual contribution to some form of influencing. But the basic will always be the same:

    • Define what “done” looks like
    • Identify a path from “here” to “done”
    • Take ownership to make sure that we get to “done”

    There you have it. Decades worth of career advice applicable to all levels and stages in your career, captured in three words: Get Things Done.

  • The plateau of meh

    The plateau of meh

    Most successful careers contain actually quite a few plateaus once observed up close. Wikipedia entries of famous people fascinate me, because they show that their paths are not as clean as one might remember.

    There is a variant of the hero’s journey that is often overlooked, because it is far less dramatic and more mundane. One where the hero does not fight the fierce monster or rises up to the insurmountable challenge. Rather, one where the hero just has to endure a slog, has to dig deep to find motivation, has to live with the fact that between epic challenges and glorious victories there are a lot of days where things just go neither right nor wrong.

    Pick a random famous person that you admire and look at their Wikipedia entry. You will find stellar achievements at the top, but once you scroll down, you get to the career plateaus where artists fight petty legal battles with prior management, where uninspired albums and movies are released, and where whole seasons are just meaningless struggle. Wikipedia entry often do not gloss over those periods or artificially dramatizes them like a lot of biographies.

    Another example is the stock market: Over a period of 20 years, the ten best days make up for more than half of the stock market. That literally means that despite healthy total returns on 99.9% of the days nothing of substance happens or even worse, massive setbacks happen. Unfortunately, it is impossible to predict those ten days. The only viable strategy is to play the long game and stay invested in the market, endure the losses with the knowledge that you will make up for it in the long run.

    The meta-achievement of any career is making it through those plateaus of utter mundaneness, keep honing your skills, putting yourself out there, increasing the luck-surface-area, being ready for the next meaningful step without knowing when and what it will be. Because one thing is true: If you keep trying and learning, the plateau of meh is temporary.

    I was reminded by all of this by Jeffrey Zeldman telling the story of his career in the advertising industry and the messiness behind every success:

    The ability to keep coming up with more ads was why this Moses-looking dude had a roomful of shiny trophies, and I did not. If I wanted a career like his, I would have to seek deeply in my soul for the strength and willingness not to give up. Career aside, if I wanted to create meaningful work, I would need to develop the patience and willingness to watch people kill my darlings, and come back with newer, fresher, better darlings. […] But keeping a positive attitude when an idea I’ve fallen in love with gets rejected remains the second most important thing I can do on a daily basis as I practice my current craft. […] The well is never dry. We only run out of ideas when we choose to stop doing the work.

    Sticking To It – Automattic Design

    Photo by Wolfgang Hasselmann on Unsplash

  • Managing Your Career Without a Manager

    Interesting post by Saswati Saha Mitra about how to take charge of your career in the absence of a manager/ leader to provide you with direction. Interestingly, the categories she lays out are also good ones to use as a manager to provide guidance to your team:

    • Craft: It was clearly vital to continue expanding my hands-on knowledge of how to do research and communicate its impact. With so many new tools and ideas emerging in our field all the time, I needed to dedicate some time to keeping up with them.
    • Connections: I also wanted to deepen the relationships I was making within WhatsApp and Meta, and to build a strong peer group that could help me learn how to do my job better.
    • Stretch opportunities: These are side projects that might fall outside of my daily remit, but would advance my growth by pushing me to explore new and interesting areas.
    • Organizational intelligence: I wanted to continue deepening my understanding of how Meta works and makes critical decisions.
    Managing Your Career Without a Manager | by Saswati Saha Mitra | Meta Research | Medium

  • Companies are not families

    Good New York Times interview with the new Peloton CEO Barry McCarthy. Near the end he dropped a nice nugget:

    And I say you’ll never hear me say we’re a family. We’re a sports team, and we’re trying to win the Super Bowl. And so we’re going to put the best players on the field we can. And if you go down the field, and we throw you the ball, and you drop it a bunch, we’re going to cut you.

    We spend the majority of our waking hours at work and with the people at work. But I always die a little inside when I hear teams talk about being a family. While it might be an alluring thought, it is neither realistic nor appealing. Family is about being bound together and in the best of cases about shared values and unconditional love.

    Work ultimately is always at the base level a transactional relationship. You work and get compensated for it. At work, you are replaceable. Everyone is. To your family, you are not. A workplace is replaceable. A family is not.

    In that regard, I’d rather aspire to establishing a community at work. One that promotes values like caring, love, a sense of belonging, respect, empathy, joy, and fairness. These might all be attributes shared with families, but there should be a clear line separating work and family.

    High functioning teams add layers on top of it like shared values, growing together and standing up for one another. But ultimately, it’s a loose band that last for a few years until it doesn’t. And that’s OK.

  • Staying Clear of Golden Apples

    Staying Clear of Golden Apples

    Rick Klau once gave one of the most influential intro presentations to Objectives and Key Results: How Google sets goals: OKRs / Startup Lab Workshop – YouTube. It’s an evergreen talk and has gotten nearly 1.2 million views over the past nine years. He recently followed up with a post What my OKRs video got wrong. In that post he mentioned that one of his key learnings is “What you and your team say no to is at least as important as what you say yes to”.

    It reminded me of a story that I often tell when introducing OKRs. It is about Atalanta, a heroine in Greek mythology. If you have watched Disney’s Brave you will notice similarities with Merida, the main character.

    Atalanta was a strong, independent woman, and she was the fastest runner in ancient Sparta. To her father’s chagrin, she did not care to get married. Her father did not agree to that plan and set up a contest in which young men would race to win her hand in marriage.

    To keep her freedom, she asked to be allowed to participate in the race herself, i.e. race for her own hand. Her father, not thinking she had a chance of winning, agreed to the deal.

    At the same time, there was a young man called Hippomenes, who fell in love with Atalanta a long time ago. The race was his chance to marry his love. He knew how fast Atalanta was, so he prayed to Aphrodite. Gossip and intrigue are nothing new, and Aphrodite didn’t like Atalanta. So, she gave Hippomenes three golden apples and told him to drop one at a time during the race to distract Atalanta. To her demise, she was so fond of those golden apples that she stopped to pick them up.

    After each of the first two apples, Atalanta was able to recover the lead, but when she stopped for the third, Hippomenes won the race. It took all three apples and all of his speed, but Hippomenes was finally successful, winning the race and Atalanta’s hand.

    Adapted from Christina Wodtke‘s Execution is everything

    If only Atalanta had set clear goals and stock to them. She would have stayed single, footloose and fancy free.

    Atalanta’s story is surprisingly timely. We all are running into golden apples every day. So much to do, so little time. However, unless we focus on a few things, we spread ourselves too thinly and what feels busy is actually distraction. OKRs help discern the trivial many from the vital few.

    The most obvious example is the selection of key results. When introducing OKRs a lot of teams start with more than five key results for each objective, because those are the metrics they are tracking. Over the course of one or two quarters most realize that focusing on three-ish key results per objective helps them focus their energy and get more done by saying no to more things.

    In other words: If at all possible, avoid the temptation of golden apples!

    Image: Herp Atalanta and Hippomenes.jpg – Wikimedia Commons

  • The dogs won’t eat it – Choosing OKRs well

    The concept of Objectives and Key Results (OKRs) is deceptively easy.

    • Objectives are ambitious, qualitative and time bound goals of a team. Each objective is typically supported by ~3-4 key results.
    • Key Results are measurable achievements that contribute to those goals. They are business outcomes and typically expressed in terms of adoption, engagement, cost, performance or quality.

    An OKR describes both what a team wants to achieve and how it is going to measure its achievement. “We will achieve $Objective as measured by $KeyResult1, $KeyResult2 and $KeyResult3.”

    At the same time, coming up with good OKRs is hard. One has to identify the few key metrics that really matter and to commit on outcomes (e.g. growth) rather than output (e.g. launching a new feature). That requires judgement, uncomfortable leaps of faith and a willingness to experiment.

    Jeffrey Zeldman tells a great anecdote in the context of Marketing that illustrates what happens if you choose your Key Results badly: The dogs won’t eat it.

  • Momentum from Day One – Getting Onboarding Right

    Momentum from Day One – Getting Onboarding Right

    Creating a good onboarding experience as a manager is tricky at the best of times. It’s even harder when you are forced to work from home against the backdrop of a global health crisis. It is harder to recognize the challenges of new hires and it’s harder for them to ramp up and integrate in the absence of ambient hallway chatter.

    At the same time, it is possible and achievable. Looking back at my own onboarding journeys, I’ve learned a lot from the good, the bad and the ugly. Most learnings are transferable into distributed settings.

    Let’s look at the bad ones first. Once, my new boss told me in our first meeting that he’s moving teams – I just relocated to the other side of the globe to work with him. That was also the job where I did not have a computer or a phone for the first week – particularly funny as I worked for a telco and had to read printed PowerPoint decks for the first week. Another time, I was put into “stealth mode” … without ever re-emerging. Or that time when I did not have a project to work on for the first two months – it was called “being on the beach” and it drove me up the walls.

    But there were also the great experiences. When my new boss walked me through everything by himself – not just giving me the opportunity to ask questions, but guiding me through what he considered important. Or when I arrived at a desk with a brand-new machine including access to all relevant systems. Or the onboarding buddy, who took it as a matter of personal pride to make sure that I had a great start.

    First impressions matter. Starting on the right foot and getting momentum is a great confidence booster for every new starter. At the same time, without guidance, new hires have to work twice as hard to learn what they need to be productive. When working from home, it takes a more deliberate effort to give new hires the necessary experiences and exposure for a solid start. Always remember that it is a bigger deal for them than it is for you. They will remember it, one way or another. Your job is to make sure those will be good memories.

    Below are a few ideas that I collected over the years.

    (more…)
  • Less is more … difficult – writing summaries

    Less is more … difficult – writing summaries

    Writing is hard and writing a summary is no exception. If you are working on proposals, general research or strategies, at some point you have to summarize your idea. As Pascal once said “I have made this longer than usual because I have not had time to make it shorter.” A summary takes time to get right.

    The investment does pay off as it makes your work easier to digest, improves structure and highlights your very best insights. It’s not uncommon that only the summary gets read. That’s actually a good thing. But it raises the stakes to get the summary right and you still need to put in the work – your summary will only be as good as the underlying work. But there are a few tips and tricks that helped me in the past.

    (more…)