PMBOK Step by Step, Part 1: The Business Case and the Project Charter

Ask people why their last project went badly, and you will hear about the schedule, the budget, the vendor or the weather. Look closer, and a large share of those problems were born earlier, at a moment nobody remembers as part of the project: the meeting where someone said "let's do it" and the room nodded. Nobody wrote down why, what the alternatives were, what it would cost if things went wrong, who was in charge or how everyone would know it had worked. The plan, the schedule and the team were all built on top of a decision that had never been examined.

This is the first article in a series called PMBOK step by step, in which I take one project from idea to closeout and walk through it the way the PMBOK Guide organizes the work, one stage per article, with the tools, the numbers and the places where the textbook needs adapting. Today is the beginning: choosing the project. We will build a business case, compare options with real arithmetic, test the decision against bad news and turn it into a project charter. In the middle there is a calculator you can use on your own numbers.

About this series and the project we will follow

The PMBOK Guide, published by the Project Management Institute, is best used as a map, not as a rulebook. It collects project management knowledge and shows how the pieces relate. Real projects do not follow the map in a straight line, but the map helps you remember what you may have forgotten. In this series I follow the stages in the order a project lives them: choosing the project, identifying who is involved, defining scope, building the schedule and cost baselines, planning for risk, running the work, keeping score and closing well. The weekly outline is on the series page, with a new part every Wednesday.

A series needs a project. For this one I chose something I know well from the inside, a small clinic, because it brings together construction, operations, people and money in a project that most readers can picture. To be clear: the project is invented. Riverside Family Clinic is a composite, not a real client, and every number in this series is illustrative. Nothing here is financial, legal or medical advice.

Here is the situation. A family physician and a practice manager see patients in a neighborhood where the nearest primary care clinic is a long drive away. Patients tell them so every week. A landlord has a vacant ground-floor suite of the right size, and the physician wonders whether to open a clinic of their own. The idea is attractive and also risky. Money, licenses, a build-out, equipment, hiring and a launch all have to come together, and the owners have a day job. This is exactly the moment where a business case earns its keep.

If you have read my guide on how a clinic opens on time, you know how much work lies between a signed lease and opening day. This series starts earlier, with the decision to begin.

Step zero: should we do this at all?

An idea is not a project. An idea is a wish with a story. A project is a decision with an owner, a budget, a date and a way to know it worked. Between the two sits a question that is surprisingly often skipped: is this worth doing, compared with the other things we could do with the same money and attention?

A business case exists to answer that question in a form that other people can read, challenge and approve. It is not a ritual for large companies. A one-page business case for a ten-thousand-dollar project and a ten-page one for a ten-million-dollar project do the same job: they make the reasoning visible before the money is spent. And visible reasoning has a wonderful side effect. It lets someone say "your assumption about demand looks high" while it is still cheap to change course.

The person who needs to decide is the sponsor, the one who owns the money and the result. In our clinic, that is the physician. A good business case is written for that person. It is short enough to read in ten minutes and honest enough to be trusted. For tips on keeping a sponsor involved after approval, see how to keep an executive sponsor engaged.

What goes into a business case

There is no single format, but strong ones answer the same eight questions.

1. The problem or opportunity. What is happening, for whom and with what evidence? Not "the neighborhood needs a clinic" but "patients in this area travel a long way for basic care, and the practice turns away new patients every week."
2. The options. At least three, always including doing nothing. If there is only one option on the page, you are not choosing, you are justifying.
3. The costs. One-time costs, running costs and the cost of delay, with the assumptions behind each.
4. The benefits. What improves, by how much, by when and who will measure it. Financial and non-financial.
5. The assumptions. The facts the numbers depend on, such as demand, prices and timing.
6. The risks. What could make the case fall apart, and what you would do about it.
7. The recommendation. One option, with the reasons.
8. The decision requested. Exactly what you need the sponsor to approve, and by when.

Notice that question five and question six are different. Assumptions are things you believe are true. Risks are things that might happen. Mixing them is a common mistake, and it hides the weakest points of a case.

The Riverside case, option by option

The physician and the practice manager sketch four options. For each, they estimate the one-time investment, the monthly benefit once the clinic runs at its expected level, the monthly cost of running it and how many months it takes to reach that level. The benefit here means the money the clinic brings in after the direct costs of seeing patients, before the fixed costs of running the place. These are illustrative figures, produced for this series.

• Option 1: Do nothing. No investment, no change. The physician keeps seeing patients elsewhere, and the practice keeps turning away new ones. The cost is not zero: it is the opportunity that stays unused.
• Option 2: Share space. Rent time in an existing provider's clinic. Investment of $110,000 for equipment and setup, a monthly benefit at full run-rate of $20,000, running cost of $11,000 a month and eight months to ramp up. Fast and cheap to start, with limited capacity.
• Option 3: Build out the full suite. Four exam rooms, a procedure room, reception and a back office in the leased suite. Investment of $420,000, a monthly benefit of $38,000 at full run-rate, running cost of $22,000 a month and twelve months to ramp up.
• Option 4: Phase it. Build the first two exam rooms and reception now, and decide on the rest after a year. Investment of $280,000, a monthly benefit of $30,000 at full run-rate, running cost of $16,000 a month and ten months to ramp up.

How should they choose? First, they agree on a rule before looking at the answers, which protects them from falling in love with a favorite. The sponsor says: payback within thirty-six months in the base case, and payback within sixty months if benefits come in twenty percent lower than expected. The second half is the important one. It asks whether the project survives bad news.

Run through the same simple model, the results are as follows. Payback means the month in which the money that came in covers the investment. The calculator below does this arithmetic, so you can test it yourself.

• Option 2, share space: payback in month 20, and month 34 with twenty percent lower benefits. It passes both tests, though its capacity limits growth.
• Option 3, full build-out: payback in month 40, and month 70 with lower benefits. It fails both tests. The full suite is a good idea that arrives too early.
• Option 4, phased: payback in month 30, and month 49 with lower benefits. It passes both tests with room to learn before committing to the second phase.

The numbers did not make the decision. They focused the conversation. The team can now say, with a straight face, that the full build-out only works if demand arrives faster than they believe, while the phased option still works if demand disappoints. They recommend Option 4, with a deliberate checkpoint at month twelve to decide on the second phase. That checkpoint, which we can call a stage gate, will come back in later parts.

Try it with your own project in the calculator. Change the investment, the monthly benefit and the running cost, and then reduce the benefit by twenty percent to see if the case survives.

Interactive tool

Does your business case survive bad news?

Loading the tool…

Benefits are not only money

The clinic will earn revenue, but that is not the only reason the physician wants it. Patients will travel less and delay care less often. Staff will have a workplace nearer to home. The neighborhood gains a service. These benefits are real, and they are easier to forget because nobody puts them in a spreadsheet.

The way to keep them honest is to give each one a measure, an owner and a date. For example, the average travel time for new patients, measured from intake forms and reviewed ninety days after opening. If a benefit cannot be measured, it is a hope, not a benefit, and it should be described as such. I wrote a full guide on this idea in benefits realization, and the benefits tracker in the toolkit gives you a ready-made sheet for the thirty, ninety and one hundred eighty day reviews.

Assumptions, risks and the "what would make us stop?" question

Every business case rests on assumptions, and the weakest assumptions deserve the most attention. For the clinic, the big ones are how many patients will come and how fast, how long it takes to be paid by insurers, what the lease terms will be and whether a qualified clinician can be hired on time. Write each assumption down with the evidence behind it, and mark the ones where the evidence is thin. These are the places to test before spending the big money, for example by asking local practices about their waiting lists.

Next to assumptions sit risks: events that might happen. A permit might take longer than expected. Equipment might arrive late. The lease negotiation might stall. The way to handle them is the one I describe in risk management for small business, and the free risk register template works well even at this early stage. Start a list now. It will become more detailed in Part 5 of the series.

One more question belongs in every business case: what would make us stop? Decide in advance which signals would cause you to cancel or change the project, for example a lease that cannot be signed by a certain date, or a cost estimate more than fifteen percent above the budget. Writing the stop signals before you are emotionally invested makes it much easier to act on them later.

Who needs to be in the room

Even in this early stage, you should know who is affected and who can influence the outcome. For the clinic, the list includes the physician who is the sponsor, the practice manager, the medical director or supervising clinician, the landlord, the lender or investor, the city office that issues permits and the neighbors. A quick power and interest sorting, as described in stakeholder mapping, will tell you who needs to be consulted before the business case is approved and who should simply be kept informed. In Part 2 of this series we will turn that quick list into a proper stakeholder register.

From business case to charter

Suppose the sponsor approves Option 4. Now the project needs to be born officially. That is the job of the project charter.

It helps to separate three documents that people confuse:

• The business case explains why, and it supports a decision.
• The project charter gives the project permission to exist, sets its boundaries and names the person who leads it.
• The project plan, which comes in the following parts, explains how the work will be done.

A charter is short on purpose. It is not a detailed plan. It is an agreement among the sponsor, the project manager and the main stakeholders about what the project is, what it is not and how decisions will be made. A good charter has these parts, shown with the Riverside Phase 1 example, still illustrative.

• Purpose and justification. Bring primary care to the Riverside neighborhood, where residents currently travel far for basic care.
• Measurable objectives. Open to patients nine months after approval. Keep total project cost within $280,000, including contingency. Reach sixty percent of planned patient visits within six months of opening.
• Success criteria. All licenses and inspections are passed before the first patient. Scheduling, records and billing systems tested end to end. Staff trained. The first week of operation runs without a system failure that stops patient care.
• High-level requirements. Accessible to people with disabilities, compliant with building and fire codes, designed for infection control and set up to protect patient privacy under the rules that apply, such as HIPAA in the United States. Check the current requirements with qualified professionals.
• Scope in and out. In: lease, design, permits, build-out of two exam rooms, a procedure room and reception, equipment, systems, hiring of the first team and launch. Out: the second phase of rooms, additional services and marketing beyond the launch.
• Summary milestones. Business case approved, lease signed, design approved, permits issued, construction complete, equipment installed, staff trained, final inspection passed, opening day.
• Summary budget. $280,000: build-out $140,000, equipment $55,000, information technology and furniture $30,000, permits and legal $12,000, launch and hiring $15,000 and contingency $28,000, which is about eleven percent of the other costs.
• Key risks. Lease terms delayed, permit timeline, equipment lead times, hiring the first clinician, demand lower than forecast.
• Key stakeholders. Sponsor, medical director, landlord, contractor, permit office, technology vendor, staff, neighbors and patients.
• Project manager and authority. Named person, with authority to approve spending up to an agreed amount per decision and to direct the work. Anything above the limit, or anything that changes scope, budget or the opening date beyond a stated tolerance, goes to the sponsor.
• Approval. The sponsor signs, with the date.

The charter is a conversation, not a form

The signature is the least important part of a charter. The most important part is the conversation that produces it. Draft the charter together with the sponsor, in an hour, sitting at the same table. Read each line aloud and ask whether you all mean the same thing by it. You will find disagreements, and every one you find now is a fight you will not have in month six.

Three tips make the conversation better. Write the objectives so they can be measured and checked by a stranger. Write the out-of-scope list as carefully as the in-scope list, since that is where future arguments begin, as I explain in how to say yes, no and not yet to scope creep. And be explicit about authority: what the project manager can decide alone, what needs the sponsor and how fast the sponsor will answer. The same attention to decision rights is part of project governance for small teams, and a simple decision log helps you keep track.

Common mistakes at the start of a project

• Writing the case to justify a decision already made. If the answer was fixed before the analysis, the analysis is theater.
• Leaving out the "do nothing" option. It is the baseline everything else must beat, and sometimes it wins.
• Using only the optimistic case. A business case without a pessimistic test is a hope with a spreadsheet.
• Vague success criteria. "Improve patient experience" cannot be checked. "Median wait for a new-patient appointment under seven days" can.
• No out-of-scope list. Scope creep starts on day one with everything you did not say no to.
• No named sponsor. A project nobody owns drifts. Name one person with the money and the authority.
• A charter that gets filed and forgotten. Reread it at every major checkpoint. If the project has drifted from it, either bring the project back or change the charter openly.

How this fits the PMBOK map

In the PMBOK Guide's process view, the work in this article belongs to the initiating stage: developing the project charter and identifying the stakeholders. Newer editions of the Guide describe much of the same work through principles and performance domains instead of a strict sequence, and they emphasize tailoring: adapting the approach to the project. The tools I use here, a business case, a comparison of options, a charter and a stakeholder list, are the same either way. What matters is that the project starts with a clear reason, a clear boundary and a clear owner.

What to do this week

Pick one project you are considering, large or small. Write a one-page business case with the eight questions above. List at least three options, including doing nothing. Run the numbers, then reduce the benefits by twenty percent and see what happens. Write the stop signals. Then draft a one-page charter with the sponsor, and ask them to read it aloud. The whole exercise takes a few hours, and it can save months.

Next Wednesday, in Part 2, we meet the people around the clinic project and build a stakeholder register: who they are, what they want and how to work with each of them. If you want the whole series at your pace, the publishing calendar shows the dates for every part, and the monthly newsletter lists each month's new parts. If you would like help turning one of your own ideas into a business case, or running a project with this level of discipline, that is what I do with Project Focus, and you can tell me where you are stuck on the contact page.

What is the question your last business case failed to answer? Tell me in the comments.

More tools. The risk register, the benefits tracker and the decision log are free in the toolkit, and a project charter template is on its way.

PMBOK and PMP are registered marks of the Project Management Institute, Inc. This series is independent and is not affiliated with, or endorsed by, PMI. The Riverside Family Clinic is an invented example, and all figures are illustrative.

Frequently asked questions

What is the difference between a business case and a project charter?

A business case explains why a project should be done and compares options so a sponsor can decide. A project charter, written after approval, gives the project formal permission to exist, defines its objectives, scope boundaries, budget and milestones at a high level and names the project manager and their authority. The plan that explains how the work will be done comes after the charter.

How long should a business case be?

As long as it takes to answer the eight questions honestly and no longer. For a small project one page is enough. For a large investment it may be ten pages. The test is whether the sponsor can read it in about ten minutes and decide.

What goes into a project charter?

A good charter includes the purpose, measurable objectives, success criteria, high-level requirements, what is in and out of scope, summary milestones and budget, key risks and stakeholders, the project manager's authority and the sponsor's approval. It usually fits on one or two pages.

Why test a business case with a pessimistic scenario?

Because estimates of benefits tend to be optimistic. If a project still pays back when benefits are twenty percent lower, the decision is more robust. If it only works when everything goes right, the sponsor should know that before spending money.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Useful Made me smile Go deeper on this

Be the first to react.

Comments

Loading comments…

Leave a comment

NameEmail (optional, never shown)

What is the question your last business case failed to answer? Post comment

Comments are reviewed before they appear. Please keep it respectful and leave links out.