Visual map · Deliver with just enough structure
Deliver with just enough structure: 55 figures.
Control scope, choose the right method, plan capacity and close projects so the lessons are used.
In this topic: Project Schedule Management: From Task List to Baseline · PMBOK Step by Step, Part 4: How Long and How Much? The Schedule and Cost Baselines · The Project Kickoff Meeting: A 60-Minute Agenda That Works · Lean Project Management: Waste, Flow and Small Batches · PMBOK Step by Step, Part 3: What Exactly Are We Building? Scope and the Work Breakdown Structure · The Project Management Plan: Ten Sections That Matter, and How to Write One in an Afternoon · Kaizen for Project Managers: Small Weekly Fixes, the Five Whys and a One-Page Card · Lessons Learned: Five Questions That Work, How to Run the Session and a One-Page Template Builder · Theory of Constraints for Project Managers: Find the One Step That Limits Everything · The Project Status Report: What to Include, How to Color It Honestly and a Builder You Can Copy · PMBOK Step by Step, Part 2: Who Is Involved? Building the Stakeholder Register · Project Management Methodologies Compared: Waterfall, Agile, Kanban and Friends (Without the Bar Fight) · Kanban for Small Teams: Finish More by Starting Less · Project Charter: What It Is and How to Write One in an Hour (Without Falling Asleep) · RACI Chart: How to Build One in 30 Minutes, With Examples and Without Drama · PMBOK Step by Step, Part 1: The Business Case and the Project Charter · Stop Scope Creep: How to Say Yes, No and Not Yet · Project Governance for Small Teams: Just Enough Structure · Agile, Waterfall or Hybrid? Choose the Method That Fits the Work · Capacity Planning: Find the Bottleneck Before It Finds You · Project Closeout and Lessons Learned That Actually Get Used
Nov 12, 2026 · 3 figures
Project Schedule Management: From Task List to Baseline
1DefineThe verbs that make the WBS
2SequenceWhat must finish first?
3EstimateRanges, not one number
4DevelopCalendar, critical path, buffer
5ControlRemaining days, every week
Critical path
Cabinet order and delivery 15→Install cabinets 3→Countertops 7→Appliances and punch list 2= 27 days
The longest chain sets the date. A week late on the cabinet order is a week late on the project.
Construction chain
Demolition 3→Rough-in 4→Inspection 1→Drywall 3→Install cabinets 3→Countertops 7→Appliances and punch list 2= 23 days
Four days of float: it can slip four days without moving the end date.
Paint branch
Demolition 3→Rough-in 4→Inspection 1→Drywall 3→Paint 2→Appliances and punch list 2= 15 days
Twelve days of float: paint can wait until the countertops are done.
Days of work for each step are in bold.
A. Demolition3 d
B. Rough-in4 d
C. Inspection1 d
D. Drywall3 d + 4 float
E. Cabinet order and delivery15 d
F. Install cabinets3 d
G. Counter-tops7 d
H. Paint2 d + 12 float
I. Appliances, punch list2 d
Finished on day 27
Day0510152025
Nov 12, 2026 · 3 figures
PMBOK Step by Step, Part 4: How Long and How Much? The Schedule and Cost Baselines
Lease negotiation and signing4 wk
Design and construction drawings6 wk
Permits and approvals5 wk
Equipment order (10-week lead time)10 wk + 9 float
Build-out14 wk
Equipment installation2 wk
Staff training2 wk
Final inspection1 wk
Opening readiness check1 wk
Project buffer4 wk
Charter target: 39 weeks
Week05101520253035
Dots, left to right: about $45k spent by month 3, about $140k by month 6 and the full base of $250k by month 9.
Nov 9, 2026 · 3 figures
The Project Kickoff Meeting: A 60-Minute Agenda That Works
Share the whyWhat problem are we solving, for whom, and how will we know it worked?
Agree the scopeWhat is in, what is out and what does "done" mean?
Clarify rolesWho decides, who does the work, who must be consulted and who just needs to know?
Show the planThe big milestones, the first 30 days and the dependencies.
Set the ways of workingHow often we meet, where we talk, how problems are raised.
1Within 24 hours, send the notes: the decisions, the actions with owners and dates, the open questions, the risks and the parking lot
2Update your documents
3Book the next meetings while everyone is still engaged: the weekly check-in and the first review
4Deliver a small first win in the first week
5Start the scoreboard
Why (the owner, 5 minutes)Invoices go out an average of 11 days after the work is done
ScopeIn, the migration of current client records and the new invoice template
RolesThe office manager is responsible for the migration
PlanFirst 30 days are data cleanup, a pilot with 10 clients and a training session.
RisksClient records with missing tax IDs, two accountants who have never used the new system, and the January rush.
Ways of workingA 20-minute check-in every Tuesday at 8:30, one chat channel, a one-page status every Friday.
Nov 8, 2026 · 3 figures
Lean Project Management: Waste, Flow and Small Batches
1Specify valueDecide what the customer actually values, in their words.
2Map the value streamDraw every step from the request to the delivered result, including the waiting.
3Create flowRemove the stops so that work moves steadily from step to step instead of in lurches and piles.
4Establish pullStart new work when there is room downstream and someone is ready for it, not because you can.
5Seek perfectionNot "make it perfect," but "never stop removing the next piece of waste." It is the same spirit as kaizen
Defects (rework)Anything done twice.
Overproduction (work nobody asked for)Making more, or sooner, than the next step needs.
WaitingWork sitting idle until someone answers, approves, signs or returns from vacation.
Non-utilized talentPeople doing work well below their skill, or ideas from the people who touch the work every day that never get heard.
Transportation (handoffs)Moving information or material from one place or person to another.
Inventory (work in progress)Everything started and not finished: open tasks, half-written proposals, unanswered requests.
Motion (hunting)Looking for the file, the latest version, the person who knows, the password.
Extra processing (gold plating)More polish, more approvals or more steps than the customer needs.
Monday: lookList everything currently open on the project, with the date each item started.
Tuesday: pick the enemyRank the eight wastes below by how often they show up and how much they hurt.
Wednesday: set a limitChoose a maximum number of open items, and write it on the board.
Thursday: cut one batchChoose one big deliverable and split it into two slices that someone can react to.
Friday: measureRecord the days from start to finish for the item you delivered, and compare it with similar items from the past.
Nov 4, 2026 · 3 figures
PMBOK Step by Step, Part 3: What Exactly Are We Building? Scope and the Work Breakdown Structure
DescriptionWhat are we doing, in two or three sentences?
DeliverablesThe tangible things the project produces.
Acceptance criteriaHow will the sponsor decide each deliverable is done?
ExclusionsWhat is explicitly not included?
AssumptionsWhat are we treating as true that might not be?
ConstraintsWhat limits the project?
It is built from deliverables, not activitiesUse nouns, not verbs: "Approved drawings
The 100 percent ruleThe pieces under any item must add up to all of that item's scope, and nothing more.
It has levelsThe project at the top
Work packages have a sensible sizeA common rule of thumb says a work package should take somewhere between eight and eighty hours of effort
VerifyThe deliverable: the team checks that it meets the requirements, using the tests you wrote.
Validate(accept) the deliverable: the sponsor or customer formally agrees that it is what they wanted.
Control scopeManage changes against the baseline.
Nov 3, 2026 · 3 figures
The Project Management Plan: Ten Sections That Matter, and How to Write One in an Afternoon
A one-week task for two peopleA half-page.
A three-month project with a small team, a vendor and a budgetTwo to five pages, built from the ten sections below.
A multi-year construction project or a large programA longer plan, often split into smaller plans
ProcurementIf you are buying a lot from vendors: how you choose, contract and manage them.
Stakeholder engagementWhen the opinions of outside people can sink the project.
Resources and equipmentWhen people or machines are scarce, as in the capacity planning article.
Assumptions and constraintsOne short list.
ApproachIf the project is agile, waterfall or a hybrid, say so in a sentence, because it changes how everything else is run.
1Start from the charterCopy the purpose, the sponsor, the success measures and the main constraints.
2Gather the three or four people who know the workPut the ten headings on a wall or a shared page.
3Write the "Out of scope" list aloudAsk the group: "What might someone assume is included that we are not doing?" Write every answer.
4Agree the milestones and the first risksDo not build the full schedule in the room.
5Name the decision-maker, the backup and the rhythmWho approves changes?
6Write it up on two to five pagesUse headings, bullets and numbers.
7Get the sponsor's approval and put it where people workA shared folder, a pinned message, a printed copy in the site trailer.
8Set a review datePlans change.
Nov 2, 2026 · 3 figures
Kaizen for Project Managers: Small Weekly Fixes, the Five Whys and a One-Page Card
1PlanName the problem, guess the cause, decide what to try and how you will tell if it worked.
2DoTry it, on a small scale, for a short time.
3CheckCompare what happened with what you expected.
4ActKeep it, change it or drop it.
DefectsDoing it again.
OverproductionMaking more than needed.
WaitingIdle time.
Non-utilized talentNot using people's ideas.
TransportMoving things around.
InventoryPiling up unfinished work.
MotionExtra movement.
Extra processingMore work than the customer values.
One slot per week, 20 to 30 minutes,At the end of an existing meeting, not a new meeting.
One improvement at a timeThe limit is what makes it finish.
A visible listA board with three columns: ideas, trying and done.
A small budget of time, not moneyAllow about 5% of the team's time for improvement.
Record decisionsWhen a change becomes the standard, note it in the decision log, with the reason.
Feed the loop with the project's own dataLate tasks, repeated change requests and recurring defects tell you where to look.
Oct 31, 2026 · 3 figures
Lessons Learned: Five Questions That Work, How to Run the Session and a One-Page Template Builder
They happen too lateAt the end of a long project, memories have faded, people have moved on and the energy is gone.
They become a blame session, or the oppositeEither someone is on trial
They list symptoms"Late deliveries." "Poor communication." "Scope changes." These are weather reports, not causes.
Nothing has an ownerA lesson without a name and a date is a wish.
Nobody looks at the notes againThe file is stored where the next team cannot find it, and even if it could, nobody would think to look.
1What did we set out to do, and what actually happened?Start with facts, in numbers where possible: the planned date and the real one
2What went well, and why?Many sessions skip this, which is a mistake.
3What did not go well, and why?Ask "why" until you reach something you can change.
4What surprised us?Surprises are the best signal of a wrong assumption.
5What will we do differently next time, who owns it and by when?This is the only question that produces change.
Is it specific?"Plan better" fails.
Does it have an owner?One person, by name, who can actually make the change.
Does it have a date?When will it be done, or when will it first be used?
Will it be seen at the right moment?The best lessons are built into something people already use: a checklist
Oct 30, 2026 · 3 figures
Theory of Constraints for Project Managers: Find the One Step That Limits Everything
1Identify the constraintFind the one step that limits the whole.
2Exploit the constraintSqueeze the maximum out of what you already have.
3Subordinate everything else to the constraintThe other steps exist to serve it: feed it clean work at the pace it can take
4Elevate the constraintOnly now, if the first three steps are not enough, add capacity: hire, buy, outsource, add a shift.
5RepeatWhen you fix the constraint, a different step becomes the weakest.
A rare skillThe only structural engineer
A decision-makerThe owner, the sponsor or the committee that meets on the second Tuesday of the month.
An approval gateA permit, an inspection, a legal review or a security review with a queue of its own.
A long-lead itemThe steel, the custom equipment, the license with an eight-week turnaround.
A shared resourceOne crew across three sites, one test environment for five teams, one kitchen for the whole restaurant.
A policy"Everything over $500 needs two signatures." A policy can be a constraint without any person or machine involved.
The ownerIn a small business, the constraint is often the person at the top
Hidden safetyPeople pad their estimates.
Shared buffersInstead of padding every task
Resources countA critical chain is the longest chain of tasks when people and equipment are also limits
Buffer managementInstead of watching each task's date
Stop multitaskingSwitching between tasks makes each one slower.
Oct 28, 2026 · 3 figures
The Project Status Report: What to Include, How to Color It Honestly and a Builder You Can Copy
The headlineOne sentence that gives the overall status and the date it applies to.
Status by dimensionSchedule, budget, scope and risk, each with a color and a one-line reason.
What was doneThe milestones reached since the last report, in plain sentences with dates.
What is nextThe two or three things that will happen before the next report, each with an owner and a date.
The top risks and issuesThree, not thirty.
Decisions and help neededThe most valuable box on the page.
Numbers that matterA few, no more: percent complete against plan
GreenThe forecast finish and the forecast cost are inside the plan, and no risk needs help from outside the project.
AmberThe forecast is slipping
RedThe forecast misses the date or the budget by more than ten percent
Friday, 10 minutes: collectAsk each owner for three lines: what finished, what is next, what is blocked.
Friday, 5 minutes: compareApply the color rules.
Friday, 5 minutes: writeStart with the headline and the decision box.
Before you send: read it as the sponsorDo the first three lines answer the question?
Oct 28, 2026 · 3 figures
PMBOK Step by Step, Part 2: Who Is Involved? Building the Stakeholder Register
Who pays?Owners, lenders, investors, grant makers.
Who decides?The people who can say yes or no, formally or informally.
Who approves?Permit offices, inspectors, licensing bodies, insurers, the landlord.
Who does the work?The team, contractors, vendors, consultants.
Who is affected?Future staff, patients, neighbors, nearby businesses, other tenants.
Who could stop it?Anyone with a veto, an appeal or a megaphone.
High power, low interestKeep satisfiedA utility company or an insurer. Make it easy for them to say yes, and do not surprise them.
High power, high interestManage closelyThe physician, the landlord, the lender, the permit office. Frequent, direct, two-way contact.
Low power, low interestMonitorWatch for changes. A person in this corner can move, so look again each month.
Low power, high interestKeep informedFuture staff and neighbors. Regular, honest updates.
Across: interest, how much they care about the outcome. Up: power, how much they can help or hurt the project.
WeeklyLook at the next contact dates and make the calls.
MonthlyRe-rate power, interest and attitude for the top ten and add anyone new.
At each milestone or gateAsk whether the people who matter for the next phase are on the list.
At closeoutRecord what worked, so the next project starts with a smarter list.
Oct 27, 2026 · 1 figure
Project Management Methodologies Compared: Waterfall, Agile, Kanban and Friends (Without the Bar Fight)
1Name the pain"We are late and surprised" and "we never finish anything" lead to different solutions.
2Change one thingNot the whole method.
3Set a ninety-day trial with two numbersFor example: how long a task takes from start to finish, and how many surprises reached the customer.
4Decide who owns the experimentSomeone must be accountable for the rhythm.
5Review honestly, then keep, change or dropPull in the team's view.
6Write the rules on one pageWhat we do each week, what the board columns mean, what "done" means.
Oct 26, 2026 · 3 figures
Kanban for Small Teams: Finish More by Starting Less
1To doWork that has been agreed but not started.
2DoingWork somebody is actively working on today.
3DoneWork that is finished according to your definition of done (more on that in a moment).
ThroughputHow many cards finish per week.
Cycle timeThe days between a card starting and finishing.
Work in progressHow many cards are open now.
AgingHow long each open card has been in progress.
Minute 0 to 5: agree on the purpose"We want to see all our work and finish more of it." One sentence.
Minute 5 to 15: put every current job on a cardInclude the small ones.
Minute 15 to 20: place the cardsTo do, Doing, Done.
Minute 20 to 25: set the first limitCount the cards in Doing.
Minute 25 to 30: agree the three rulesDefinition of done, red cards for blocked items and a fifteen-minute review each week.
Oct 24, 2026 · 3 figures
Project Charter: What It Is and How to Write One in an Hour (Without Falling Asleep)
The business caseSays why this is worth doing, comparing options, costs and benefits.
The project charterSays yes, we are doing it, and this is the box we are doing it in.
The scope statementDescribes in detail what is included, often after the charter.
The project planExplains how, with tasks, dates, owners and risks.
1Project nameShort, memorable and not "Project Phoenix 2.0 Final v3." A name people can say without sighing.
2PurposeWhy does this project exist?
3ObjectiveWhat will be true when we are done?
4Success criteriaHow would a stranger check that we succeeded?
5Scope: inWhat is included?
6Scope: outWhat is not included?
7Budget and deadlineHow much and by when?
8Key stakeholders and rolesWho is the sponsor, who is the project manager, and who else matters?
Minutes 0 to 15: interview the sponsorAsk the ten questions.
Minutes 15 to 35: write the draftOne page.
Minutes 35 to 50: read it to two people who matterSomeone who will do the work and someone who will be affected.
Minutes 50 to 60: fix it and send it for signatureKeep the first version, so you can see later how the project moved.
Oct 23, 2026 · 3 figures
RACI Chart: How to Build One in 30 Minutes, With Examples and Without Drama
R is ResponsibleThe cook who actually makes the dish.
A is AccountableThe head chef, or the owner, the one who answers if the dish is wrong, late or cold.
C is ConsultedThe person who is asked before the decision
I is InformedThe person who is told after the decision or when the work is done: the waiter who needs to know the special sold out.
| Task | Who |
|---|---|
| Request the change in writing | Whoever wants it is R, the Owner's representative is A for logging it |
| Price the change | General contractor is R, Owner's representative is A (they check the price is fair), Designer is C |
| Check the effect on the schedule | General contractor R, Owner's representative A, Designer C |
| Approve or reject | Owner is A, Owner's representative is R (prepares the recommendation), Designer and General contractor are I |
| Update the budget and the log | Owner's representative A and R, Owner I |
A schedule shows when
A stakeholder map shows who matters and how to engage them
A decision log records what was decided and by whom, which is the memory of the A column
A project charter names the project manager and their authority
Lightweight governance keeps the whole thing from becoming bureaucracy, as I explain in project governance for small teams
Oct 21, 2026 · 3 figures
PMBOK Step by Step, Part 1: The Business Case and the Project Charter
The problem or opportunityWhat is happening, for whom and with what evidence?
The optionsAt least three, always including doing nothing.
The costsOne-time costs, running costs and the cost of delay, with the assumptions behind each.
The benefitsWhat improves, by how much, by when and who will measure it.
The assumptionsThe facts the numbers depend on, such as demand, prices and timing.
The risksWhat could make the case fall apart, and what you would do about it.
The recommendationOne option, with the reasons.
The decision requestedExactly what you need the sponsor to approve, and by when.
Option 1: Do nothingNo investment, no change.
Option 2: Share spaceRent time in an existing provider's clinic.
Option 3: Build out the full suiteFour exam rooms, a procedure room, reception and a back office in the leased suite.
Option 4: Phase itBuild the first two exam rooms and reception now, and decide on the rest after a year.
Oct 19, 2026 · 2 figures
Stop Scope Creep: How to Say Yes, No and Not Yet
1Write it downThe requester describes the change and why it matters, in a sentence or two.
2Assess the impactThe project team estimates the effect on time, cost, quality and risk, and whether it displaces other work.
3DecideThe right person approves, rejects or defers.
4Record and updateIf approved, update the plan, the budget and the baseline, and log the change.
Yes, with a priceIt takes about this much more time and money. Approve it, or swap it for something already planned.
No, with a reasonTied to the sponsor's own priorities, not to convenience.
Not yetA great idea that does not fit this phase. It goes on the list for the next one.
Oct 19, 2026 · 2 figures
Project Governance for Small Teams: Just Enough Structure
RolesWho is the sponsor, the owner, the project manager and the contributors.
RhythmWhen the team reviews, when the sponsor reviews and when the project is formally checked.
Decision rightsWho decides what, and up to what threshold.
GatesA few checkpoints with criteria to continue, change or stop.
RecordsA short log of decisions, risks and changes.
| Decision | Who decides |
|---|---|
| Spending within the approved plan | The project manager, up to an agreed amount |
| Spending above that amount, or any use of contingency | The sponsor |
| Changes to scope, time or budget | The sponsor, following the change process in how to stop scope creep |
| Day-to-day task assignment | The project manager and the team |
| Hiring, firing and contracts | According to company policy, with the sponsor informed |
| Stopping or restarting the project | The sponsor or a small steering group |
Oct 19, 2026 · 1 figure
Agile, Waterfall or Hybrid? Choose the Method That Fits the Work
Clear requirements, cheap changeMixed: a hybridFix the goal and the limits, and let the uncertain parts run in short cycles.
Clear requirements, costly changePlan-drivenInvest in planning and review before committing.
Unclear requirements, cheap changeAgileBuild in small steps and learn by doing.
Unclear requirements, costly changeMixed: a hybridPlan the costly parts, iterate on the unclear ones.
Across: how expensive it is to change course late. Up: how clear the requirements are.
Oct 19, 2026 · 2 figures
Capacity Planning: Find the Bottleneck Before It Finds You
1Identify the constraintFind the one step, resource or policy that limits the whole system.
2Exploit itMake sure the constraint is never idle and is spending its time on the most valuable work.
3Subordinate everything elseAdjust the rest of the system to support the constraint.
4Elevate the constraintIf it still limits you, invest to increase its capacity: add people, tools or hours.
5RepeatOnce the constraint is relieved, another one becomes the limit.
Oct 19, 2026 · 2 figures
Project Closeout and Lessons Learned That Actually Get Used
AcceptanceFormal confirmation from the right person that the deliverables meet the agreed criteria.
HandoverEverything the people who will run, use or maintain the result need, delivered and understood.
Contracts and financesFinal accounts, outstanding invoices, supplier closures, retentions and any claims settled or documented.
Releasing resourcesPeople reassigned, equipment returned, access and licenses closed.
Benefits ownershipA clear handover of the business case to the owner who will track and realize the benefits
Lessons learnedReflection captured in a form that can be used.
RecognitionThanking people and acknowledging contributions.
RecordsDocuments, decisions and data archived in an organized place.
DocumentsDrawings or designs as built, manuals, configurations, warranties and certificates in one organized place.
ContactsWho to call for each system or supplier, with real names.
TrainingHands-on sessions for the people who will operate and maintain it.
Open itemsA clear list of what remains, with owners and dates.
Support periodAn agreed time, such as thirty days, during which the project team remains available to fix teething problems.
Next step
Want these ideas applied to your business?
Every figure starts from a real situation. Tell me yours.