43
18 Comments

The BUS method for getting unstuck

The following passage was transformative for me when I first encountered it back in college. It helped me get unstuck on a novel I was working on, and since then I've used it in just about every other domain — especially business — where there's no clear blueprint for how to reach an objective.

From Robert M. Pirsig's Zen and the Art of Motorcycle Maintenance [1]:

“I want to write a letter to Mom,” Chris says. … He puts the paper in front of him, grabs the pen in a heavy grip and then concentrates on the blank paper for a while. He looks up. “What day is it?”

I tell him. He nods and writes it down. Then I see him write, “Dear Mom:” Then he stares at the paper for a while. Then he looks up. “What should I say?”

I tell him getting stuck is the commonest trouble of all. Usually, I say, your mind gets stuck when you’re trying to do too many things at once. What you have to do is try not to force words to come. That just gets you more stuck. What you have to do now is separate out the things and do them one at a time. You’re trying to think of what to say and what to say first at the same time and that’s too hard. So separate them out. Just make a list of all the things you want to say in any old order. Then later we’ll figure out the right order.

“Like what things?” he asks.

“Well, what do you want to tell her?”

“About the trip.”

“What things about the trip?”

He thinks for a while. “About the mountain we climbed.”

“Okay, write that down,” I say.

He does. Then I see him write down another item, then another, while I finish my cigarette and coffee. He goes through three sheets of paper, listing things he wants to say.

“Save those,” I tell him, “and we’ll work on them later.”

The "BUS method" is my formalized version of Pirsig's insight. It has three parts: 1) brain dump, 2) unbundle, 3) structure. Here's a quick breakdown:

Brain dump ideas under a stated objective.

Start by writing down the problem you're trying to solve in a single sentence. Then set a timer for 5 or 10 minutes and free write [2] about the problem until the time elapses. Free writing is when you write in an unpremeditated way without pausing to reflect on what you’ve written. No worrying about typos, capitalization, grammar, or even paragraph breaks. You simply dump your thoughts out and let the associative networks of your brain take the lead. If your mind draws a blank at any point, fall back on default phrases like “this and that and the other thing,” until you find new things to say.

Unbundle the dumped ideas into discrete units.

Break up the paragraph into a list of separate items and delete all of the useless nonsense (for me, this is often 50%+ of the content). Then eliminate redundancies by grouping related ideas together. Don't fuss over things like grammar or chronological order on this step.

Structure the unbundled ideas into action items.

Now that the ideas are unbundled, you can finally make use of them. Consider fine-tuning each item on the list and then arranging them into a chronological sequence of action steps that you can "export" to a to-do list or project-management system.


The Adjacent Possible is where I share my most useful insights in bite-sized posts. One email per month. Many insights per email:

Go here for more posts in the series.


Footnote:

[1] Click here to read the full passage from the book.

[2] I personally use this freewriting app from Squibler. You can't stop writing once you start or else all of your progress gets deleted.

  1. 5

    This story can't be understated especially in the context of large knowledge work projects, where we face a huge obscure daunting task without a clear path defined for us.

    My first job as a SWE I didn't have a great PM tracking my progress for multi-month projects, so I would just sit there in paralyzing anxiety knowing this huge project needs to get done, and ironically end up getting nothing done compounding the anxiety in an insidious feedback loop.

    Anyway I learned the hard way that the only way forward is to relax, write down everything that needs to get done, organize it, and do a manageable task every day. Seems so logical, but us humans don't always operate logically when faced with hard things.

    I have a feeling a lot of people who successfully procrastinated through school end up with this problem in the workplace.

    1. 2

      I would just sit there in paralyzing anxiety knowing this huge project needs to get done, and ironically end up getting nothing done compounding the anxiety in an insidious feedback loop.

      This describes what it's like for a huge % of new entrepreneurs in the first weeks/months of starting a business. Navigating the unknown unknown is a skill you have to learn.

  2. 3

    Almost everything is better to do it first and then iterate. Just sitting there waiting for a miraculous idea and then achieve a success from that idea is almost never happen or the possibility is lower than trying things out.

    Overtime you start being comfortable of not knowing stuff but just doing it anyway.

    That is why always start small and aim big.

    Here more about start small and aim big : Be patient to start small while thinking big

  3. 2

    Interesting concept. Yes, it helps to write the first draft without thinking much about the entire scope, and then narrow down and refine as we want to get better.

  4. 2

    This.
    This is probably one of the most important and helpful posts I've stumbled upon on IH. My main struggle is getting stuck in almost all areas of my life.
    Thank you for sharing. 🫶

  5. 2

    That actually helped me a lot. You also should try to use a microphone as a variant. Sometimes speaking makes generating ideas better and even funny.

  6. 2

    I love the idea of a brain drump. Do you do a single dump for all your thoughts or start with a specific intent and do a session writing down your thoughts around that?

    1. 1

      I've done both, but these days I like to start with a specific intent.

      A good way to think about it is "explore vs exploit." Explore: if you're in-between projects and don't know what you want to do broadly, you might do a free writing session with no agenda whatsoever. Exploit: if you're already involved in 1+ projects but don't know how to get from point A to point Z, free writing can help uncover the path to B, then to C, then to D, etc. To "cross the river by touching the stones," as Deng Xiaoping used to say.

  7. 2

    Well, funny enough, I've been having a similar -and unexpected- problem solving experience.

    It happens when I share my webapp dev struggles with my developer friend on whatsapp. This forces me to write down the issue in a way he will understand. And guess what, most of the time, the process of writing it down and reviewing what I am about to send has led me to the solution!

    1. 2

      It happens when I … write down the issue in a way he will understand. And … the process of writing it down and reviewing what I am about to send has led me to the solution!

      Yes! What you're doing is called rubberducking. It's similar to the BUS method in that it ultimately helps you gain clarity about the work you're doing. Yet from a cognitive perspective, the two techniques are polar opposites.

      The BUS method is about tricking the analytical networks of your brain to shut off so the creative networks can do their thing. Rubberducking is about tricking yourself to be more analytical through role play as a teacher. Good stuff either way.

      1. 2

        And... that's why ChatGPT is so great. It's a rubber duck that talks back. ;)

    2. 1

      This comment was deleted a year ago.

  8. 1

    This is somewhat everyone need !!!!! So cool.....

  9. 1

    The struggle I run into is creating such a long list from my brain dump that I can get overwhelmed.

    Not only that, but as I check things off the list, the list grows larger as I explore each point and implement them.

    1. 2

      In such cases, using a prioritization matrix might help. 🙂

  10. 1

    Very cool, I'm afraid I will have to test this structure already tomorrow 😅. Thanks for sharing!

  11. 1

    Cool framework, I always struggle with the last part - structure most. Forever dump ideas and play with them:D

  12. 0
    1. Brain Dump:

    The first step of the "BUS method" is the Brain Dump. It's the initial phase where you confront a problem or objective head-on. Here's a more detailed breakdown:

    a. Define the Objective: Start by defining your problem or objective in a clear, concise sentence. This sentence acts as your guiding light throughout the process.

    b. Set a Time Limit: Time constraints are essential to prevent overthinking and perfectionism. Set a timer for 5 to 10 minutes, depending on the complexity of the task.

    c. Free Writing: Engage in free writing during the allocated time. Free writing means you write without inhibitions. Don't worry about grammar, punctuation, spelling, or paragraph structure. It's about letting your thoughts flow freely onto the page. If you encounter writer's block or find yourself stuck, employ stock phrases or placeholders to keep the flow going.

    d. Explore All Angles: During this phase, explore all angles of the problem or objective. List ideas, questions, concerns, potential solutions, or any other relevant thoughts. The goal is to exhaust your initial thinking on the topic.

    1. Unbundle:

    Once you've completed the Brain Dump, it's time to move on to the Unbundle phase. This step involves dissecting the content you've generated during the Brain Dump. Here's how it works:

    a. Create Discrete Units: Take the content you've written and break it down into discrete bullet-list items. Each item should represent a single idea, task, or aspect of the problem. The goal is to simplify and clarify the content.

    b. Eliminate Useless Content: During the Brain Dump, it's common to generate a lot of content that may be irrelevant, repetitive, or incoherent. In the Unbundle phase, ruthlessly eliminate this unnecessary content to streamline your thoughts.

    c. Group Related Ideas: Organize the remaining items by grouping related ideas together. This step helps in identifying patterns, themes, and connections among your thoughts.

    1. Structure:

    The final phase of the "BUS method" is Structure. This step involves transforming the unbundled ideas into a structured plan of action. Here's a detailed breakdown:

    a. Fine-Tune Each Item: Go through each item on your list and refine it for clarity and coherence. This may involve rewriting, rephrasing, or adding additional context as needed.

    b. Create a Sequence: Arrange the refined items into a chronological sequence of action steps. Think about the logical order in which these steps need to be executed to achieve your objective.

    c. Export to Actionable Format: Once you have a structured list of action items, you can export them to a to-do list, project management tool, or any other format that suits your workflow. These action items become your roadmap for tackling the problem or achieving your objective.

    In summary, the "BUS method" is a systematic approach to problem-solving and task management. It allows you to unleash your creativity and brainstorm effectively (Brain Dump), refine and simplify your ideas (Unbundle), and then transform those ideas into actionable steps (Structure). Whether you're working on a novel, solving a complex business problem, or managing projects, this method can help you break down and conquer tasks more efficiently and effectively

Trending on Indie Hackers
How I Launched My AI Startup with a Warm Email List and Zero Marketing Budget? 31 comments Here's how we got our first 200 users 29 comments What you can learn from Marc Lou 20 comments Reaching $100k MRR Organically in 12 months 15 comments Software Developers Can Build Beautiful Software 13 comments Worst Hire - my lessons 11 comments