Michael Rill

Einfach machen

Tag: writing

  • 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.

  • Using brevity to write better

    Using brevity to write better

    For the past few years there has been a meme in the system about document-based cultures. I’m a big proponent of writing as a tool to sharpen thinking. At the same time, documents and writing are only a tool and not the goal in itself. All too often I find myself staring at a 15-pager with little structure and hard to identify key insights.

    The hard truth is: It is hard to hold the attention of an audience for 15 pages. But 15 pages is a good start. Take those and turn them into six pages. Six pages that provide enough context, lay out the challenge or opportunity that you are addressing, and what kind of change you want to drive and how. This requires making deliberate decisions on what is important and what isn’t. The goal is not to get as many points across as possible, but to land the few critical points safe and sound. Six pages seem to work well, but it if you can do it in four or three pages, go for it.

    Try to optimize not for brevity, but also for readability. Make sure that you use headings and sub-headings to help the reader with a structure. Use bulleted lists, and if the list has an order, use numbered lists. Write your sentences with simple words and avoid complex sentence structure. Form follows function. Do not optimize your sentence structures to fit a word count, but rather make them easy to read. If sentences sound complex, they are. Use features like “Read Aloud” to have your text read to you. Tools like Hemingway Editor also make your text more readable.

    Use the spell and grammar check to avoid unforced errors. Do not fiddle with line spacing, font size, spacing or page margins. The defaults work well for 99% of all documents. If you have data, go splurge on a chart.

    If there are gems that didn’t make it into the six pages, put them into the appendix. And make the appendix a separate document. Now you have a tight six-pager.

    Now turn the six-pager into a one-pager. Boil your message down to one page – still providing sufficient context, easy to read, well-structured, focusing on what change you want to drive and how. Again, do not fiddle with font-size etc. You don’t need it. By now you know your key messages and it rarely takes more than an hour to get the first draft of the one-pager.


    Now turn the one-pager into three bullets. They express the essence of what you want to advocate for. When you share your document, put those bullets into the email. Then link to the executive summary and your six-pager. While this takes time, it will improve your ideas. Ultimately, you want to get your reader to the point as fast as possible. Do not make your reader pay for all the good thinking and research that you have done.

  • Categories for journaling

    Over the past few years, long-hand journaling helped me reflect and think through many personal and professional topics. Ofir Sharony offers a nice framework to establish a journaling routine.

    “Start by shutting down all interruptions: disable Slack mentions and email notifications, place your phone out of sight, and enter your flow by wearing your noise-canceling headset. Once you feel focused, go over today’s calendar, skim through your to-do list, and reflect [on one or more of] on the following:

    1. Creations: What did you create today?

    2. Decisions: What were the top decisions you made today?

    3. Insights: What interesting ideas did you or others raise today?

    4. Challenges: What were the main challenges you faced today?

    5. Tomorrow: How do you make the most of tomorrow?”

    Leadership journal: become an inspiring leader | Medium

    It’s a nice structure and allows us to process what happened today to learn and improve for tomorrow. Little by little.

  • There is something in the air

    There is something in the air

    Ever since the whole web3 conversation gained momentum it feels like a renaissance of blogs is coming. I don’t know whether it is the explanation of web3 within the context of Web 1.0 and Web 2.0, or the discussion of decentralization away from the big platforms, or something else. In his State of the Word, Matt mentioned that one of the most web3 things one can do is registering their own domain. He also recently asked people to write more. Others like former Blogger product manager Rick Klau picked up his blog again and Hunter Walk seems to be blogging more frequently these days. And OGs like rands, MG Siegler, Gruber and Kottke continue to blog like it has never gone out of style. It is just a gut feel, but like Vinyl picking up again, it feels like there is an underlying current of people rediscovering their love of blogs.

    Make no mistake, I don’t think that blogs (and its many derivatives like Tumblr) will challenge current or future social media. At the same time, the number of internet users is one or two orders of magnitude bigger than ten or 15 years ago. And a small portion of a large number tends to be a large number. And that is awesome. Maybe we are even in for better tools for reading and commenting on blogs – RSS for blogs seems to be in stasis ever since Google Reader shut down.

    I’m fascinated by looking at personal blogs from way back when. Florian, a friend of mine, started writing a blog back in 2005 when he moved to Ireland. He still posts a few times a year. That doesn’t seem much, but over the course of 17 years it adds up. Isaac started his blog in 2002, but unfortunately stopped writing in 2015. It is still wonderful to browse through his archive as moments in time. I even resurrected and went through my own old blog archive – I even found an old Blogger blog going way back to 2004. Nothing deep and earth shattering, but that’s not the point. Blogs document moments in time. Nothing more, nothing less.

    My point is: Blogging might get another moment, it might not. Both are fine. There is intrinsic value of blogging in terms of sharpening one’s thinking, sharing ideas and documenting moments for my future self. None of that requires an audience, engagement or virality. If a tree falls in a forest and no one is there, does it make a sound? If I blog and no one reads it, does it matter? Who cares! By the time I hit publish, I’ve already gotten a positive return on investment. And as long as I use open source software that runs on my own domain, that’s a pretty future proof investment.

  • 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…)
  • How to get more out of OneNote

    OneNote is one of those underappreciated apps within Office 365. To be honest, I’ve only used it for the last two years despite my wife having praised it for her work as a teacher for a long time. But it really has grown on me and I enjoy taking notes, working on outlines and reviewing documents with OneNote. Its integration with Teams makes it a no-brainer to share notes among a project team.

    I recently saw an unanswered tweet asking for help about OneNote and thought this might be an opportunity to share some of the things that I’ve learned to appreciate about OneNote over the last two years.

    (more…)
  • Writing well, often

    Writing well, often

    I very much believe in the power of good writing. As such I admire the good work of companies like Mailchimp and Slack to promote good writing that is more approachable. Hence I was delighted when Anna Pickard started publishing some of Slack’s content style guide and writing principles. They follow Mailchimp’s great work, who published their voice and tone style guide already last year.

    At work me and my team started writing a monthly newsletter. It started out as a mailing just for the broader team to help us understand what everybody else is working on. However, people enjoyed reading it and started sharing. Now we have a group of family and friends throughout the organisation that loves reading this newsletter every month. Although it might seem insignificant, it is one of the highlights of my job. It is a chance to connect with people, find out what they are working on and spread the good news. The newsletter is very different from other corporate emails, as we aim to write it in very accessible language (thank you Mailchimp and Slack for setting such good examples). We spend a good amount of time to get it right, and people appreciate it.

    When I saw Anna speak earlier this year at Webstock, it clicked with me, why it was so hard and how we can make our job easier: Each month we were trying to figure out how to write a good newsletter from scratch, based on our experience. And even worse, we all did it individually. As a result, writing the newsletter took a lot of time and effort to make it sound right with good content and a consistent voice. We needed to reflect on what people love about the newsletter, why they read it despite their own email overload and write it down. This helps February-Michael be as good as January-Michael, and James write with the same passion as Elizabeth and vice versa.

    Below are the guidelines we came up with. In fact, the whole thing became a manifesto that was fun and empowering to write in itself. It borrows heavily on Anna’s talk and if we’ve done a good job, hopefully somebody will borrow heavily from us. Maybe it provides inspiration for somebody to start sharing more of their own story through a blog or a newsletter. Believe me, it is fun and better things will happen the more open you are.

    (more…)
  • On writing – Where Creativity, Fear and Action go on a road trip

    On writing – Where Creativity, Fear and Action go on a road trip

    Any creative endeavour is an adventure. It takes us from here to somewhere new, hopefully somewhere exciting. That sounds simple and exciting in itself, but the devil is in the detail and once we embark on our adventure, we notice that things turn out to be trickier than previously imagined.

    Let’s take writing as an example.  Everyone knows the situation: we’ve got a wonderful idea, something to say and we want to share that idea. So we sit down and start with a blank sheet or screen. We write our first words, realise that they don’t really work so we start over again, start differently, it still doesn’t work. We get frustrated, doubt creeps in. Maybe we aimed too high and the idea was not as good as we thought it was. We really want to put ourselves out there, but worry that we are not good enough. We start checking our email, then Facebook, then Twitter, post the picture of our lunch on Instagram, then go back to email. At some point we declare defeat and leave the idea altogether.

    That’s how many writing efforts end – the adventure stops before it even really begins. And that’s sad, because the world likes adventures and needs more of them. Let’s find out why it is so challenging by borrowing from two concepts:

    (more…)
  • Writing good copy

    Writing good copy

    I write a monthly newsletter at work. Our team is distributed across three continents and too many timezones. From time to time things slip through the cracks and you hear the inevitable “I wish I had known that earlier”.  The newsletter tries to close the space between the cracks and helps people know what’s going on. It is also a welcome place to highlight the great work that people contribute to the team.

    I very much enjoy writing it. It’s a highlight of my month, because I can channel the best person I want to be: fun, enthusiastic, empathetic, helpful, … My objective is to write in the tone that I would like to have a good conversation in. As a German, I’m a non-native speaker in Australia and tend to overthink and over-structure my sentences when I speak. I choose words deliberately and it’s common to hear me talk in numbered lists. The newsletter is an opportunity for me to freshen it up. And it works: people enjoy reading the newsletter, they forward it – even our CEO reads it. Not bad for a 30 people team in a company of 40,000.

    My big secret is that I copy the newsletter. Not the content, that would be obscure. But I try to channel my inner Slack. They have such a wonderful tone all their copy, be it tweets, quirky messages when you open their app or even release notes for software updates. Anna Pickard is Editorial Director at Slack helped create that tone:

    It is sometimes funny, sometimes serious, sometimes just plain and informative, but throughout, it should feel like nothing more than a person, talking to another person. Human to human […] making sure we’re treating people with respect, empathy and courtesy all the way through. […]We want people to like using Slack, and to want to share the experience. 

    Slack’s Editorial Soul: Anna Pickard
    on Writing the Brand Experience

    And the best thing: they got their inspiration from Mailchimp, who have been kind enough to publish a Style Guide for Content. I’ve only dipped my toe into it for now, but it looks like a wonderfully written guide on how to write well, especially the section on Voice and Tone. Mailchimp rules and I love them for doing this.

    Once you manage to have good topics and write them up well, you have a winning formula to make a lot of people’s lives easier and happier.

    Photo credit: Martin uit Utrecht / Foter.com / CC BY-NC-SA

  • Bad writing is a meeting factory

    From Guilded, a Seattle web design & engineering firm, comes a nugget around why good writing is so important:

    Bad writing is a meeting factory. Being able to articulate a thought in writing means your team gets to take advantage of asynchronous communication. Whereas meetings are synchronous— requiring all parties to be present and engaged for the duration of the communication event—written communication is asynchronous, meaning the recipient can address your request or idea on their own time.

    Source: Software is 10% Code