Frequently asked questions about thinking, epistemology, and cognitive tools. 1668 answers
Pick one system you operate daily — your morning routine, your email processing workflow, your content pipeline, your exercise habit. Map every step as a sequential station. For each station, write down how long it actually takes (not how long it should take). Circle the longest station. That is.
Choose a system you operate that feels stuck — one where effort has not produced proportional results. It could be a creative pipeline, a fitness routine, a learning practice, or a work process. Map it as a sequence of stages, then run a five-day diagnostic. For each stage, track two things: (1).
Map one of your recurring personal workflows using Goldratt's Five Focusing Steps. Step 1 — Identify the constraint: Choose a process you repeat at least weekly — preparing a report, processing your inbox, completing a creative project, studying a new skill. List every stage of the process and.
Conduct a personal bottleneck audit over the next three working days. Step 1: Each evening, review your day and identify every moment where your throughput stalled — where you felt stuck, distracted, drained, or unable to move forward on something that mattered. Write down what you were doing and.
Choose the bottleneck you identified in L-0944 (or your strongest suspicion about what constrains your throughput). Design a measurement protocol: What specific metric will you track? What unit does it use? How will you collect it? For one full work week, measure that constraint daily. At the end.
Take the bottleneck you measured in L-0945 — the constraint with a baseline number attached to it. Conduct a waste audit. For the next three working days, every time you are actively engaged with your constraint (your deep work block, your decision-making window, your creative session, whatever.
Identify three non-bottleneck processes that currently feed into or interrupt your constraint (the bottleneck you identified and exploited in L-0945 and L-0946). For each one, answer: How much output does this process produce per day? How much of that output can my bottleneck actually consume per.
Return to the bottleneck you have been measuring and exploiting throughout this phase. Write down your current throughput at the constraint after exploitation and subordination. Below it, write the throughput you need to keep your system flowing without accumulating queues. If the gap is zero or.
Return to the bottleneck you have been working on throughout this phase. Assume, hypothetically, that you have fully resolved it — that the constraint is gone, throughput at that stage is unlimited. Now ask: where does the queue build up next? What stage of your personal system would become the.
Take the system you have been analyzing throughout this phase. Map every step from input to output. For each step, estimate its maximum throughput — the most units it could process per time period if nothing upstream were constraining it. Now mentally remove the current bottleneck. Which step has.
Identify one collaborative workflow you participate in — at work, in a side project, or in a household. Map every step that requires a specific person''s involvement before the next step can proceed. For each person-dependent step, count how many items are currently waiting for that person. If you.
Pick the single workflow you perform most frequently — the one you do daily or multiple times per week. Time each discrete step of that workflow with a stopwatch or timer. For each step, mark whether you are actively thinking and creating, or waiting for a tool to respond (loading, processing,.
Pick one recurring process in your work or personal life — something you do at least weekly. Map every step from trigger to completion. For each step, classify it as one of three types: (1) value-adding — this step directly produces the output or moves it meaningfully forward, (2) necessary.
For the next five working days, keep an information request log. Every time you need a piece of information to proceed with a task — a number, a document, a clarification, a dataset, an answer — write down: (1) what you needed, (2) where you looked first, (3) how long it took to obtain, and (4) in.
Open your task manager, project list, or inbox. Identify every item where the next action is a decision only you can make. Count them. For each one, write down the date it first became decidable — the date you had enough information to choose, even if imperfectly. Calculate the average wait time..
For one full work week, conduct an energy audit. At four fixed times each day — upon starting work, at midday, at mid-afternoon (around 2-3 PM), and at the end of your workday — rate your cognitive energy on a 1-to-5 scale where 1 means you cannot sustain focused thought and 5 means you are at.
Identify your current binding constraint — the bottleneck you have been measuring since L-0945. Write it on a physical sticky note or index card in this format: '[Bottleneck name]: [current metric value] / [target value].' Place it where you will see it at least ten times per day — on your.
Identify the single step in your most important workflow that fails most often or degrades most under pressure — your known constraint point. Design three buffers for it: (1) a time buffer — schedule 20% more time than the step typically requires; (2) a stock buffer — maintain one completed output.
Open whatever capture tool you will actually use — a notebook, a spreadsheet, a daily note in your knowledge system — and create your first bottleneck journal entry right now. Record today's date. Write one sentence naming the constraint that most limited your throughput today. Rate its severity.
Build a complete Bottleneck Analysis Operating Document for one personal or professional system. It should contain: (1) a value stream map of every stage, with measured cycle times and queue sizes from at least three cycles of observation; (2) a constraint identification section naming the current.
Open your calendar and task list right now. Count every commitment you have made for this week — meetings, deadlines, projects with expected deliverables, personal obligations. Write the total number down. Now estimate your actual deep-work hours for the week: take your waking hours, subtract.
For the next five working days, track your focused work time with a timer. Start the timer only when you are producing meaningful output — writing, designing, coding, analyzing, building. Stop it when you switch to email, meetings, browsing, or any non-output activity. At the end of each day,.
Calculate your sustainable pace. Take the capacity measurement from L-0962 — your actual average productive hours per week over at least two weeks. Subtract 15% as a variance buffer for unexpected demands, illness, and maintenance tasks. The result is your sustainable weekly pace. Write it down:.
For the next five workdays, rate your capacity on a 1-to-5 scale within the first 30 minutes of your morning. Use this rubric: 5 = rested, clear-headed, energized; 4 = solid, minor drag; 3 = functional but flat; 2 = foggy, low energy, distracted; 1 = depleted, sick, or emotionally overwhelmed..