What to do when the client wants a Gantt chart

The book has no chapter on this, because nobody at Basecamp asks for one. A client does, usually in the first meeting, and often because a previous agency gave them one.

A Gantt chart shows tasks as bars against a calendar, with dependencies. Shape Up deliberately avoids task-level plans, so the request can feel like a contradiction. It is easier to deal with if you ask what the chart is for.

What they are really asking for

Clients ask for a Gantt chart to answer one of a few questions.

• When will it be done, so I can plan a launch?
• Is the project on track, so I can tell my boss?
• What is each of you working on, so I know I am getting value?
• What do you need from us, and when?

Each of these has a Shape Up answer that does not need a task-level estimate. Ask the client which question they have. Often it is the first or the second.

Give them dates

A cycle has a start date and an end date, fixed at the betting table. That is a firmer commitment than most Gantt charts offer, because it does not depend on estimating dozens of tasks correctly. Put the cycle calendar on one page: bet, build, cool-down, next bet. For a client with a launch date, this is the chart they were after.

What you cannot give is a promise of every feature on every date. The pitch’s core flow is the commitment. The rest is the flexible part, and chapter five covers how to write that into the contract.

Give them progress

The hill chart from the last chapter answers the “on track” question better than a Gantt chart does, because it shows uncertainty. A Gantt chart that shows every bar on schedule can hide a problem until it is too late. A dot stuck uphill shows it in the first week.

Give them a view of what is happening

A list of the scopes, with an owner and a one-line status for each, serves the “what is everyone doing” question. The team can keep it in whatever tool they use. It describes outcomes, not hours.

Give them a Gantt chart anyway, if you must

Some clients cannot proceed without one. Procurement requires it, or their own management insists. In that case, draw it at the level of the cycle and the scopes, with bars as wide as the cycle. Label it as the plan for the bet. Do not break scopes into tasks with dates, because those dates will be wrong and you will own them.

Say what the chart is: a calendar for the cycle, with the hill chart as the real status. If the client accepts that, you have a document that satisfies their process and leaves your method alone.

Where to hold the line

Refuse to estimate tasks. Refuse to promise scope in weeks that the pitch has not been shaped to support. Refuse to treat the Gantt chart as the contract. These three keep the method intact, and you can usually explain them in one sentence: the date is fixed, the scope flexes and the report shows where things stand.

Clients tend to accept this more readily once they have seen one cycle finish on its date. The first conversation is the hard one.

Questions people ask

Why does a client ask for a Gantt chart?

Usually because they need to plan around your work: a launch, a campaign, a board meeting. The chart is a means of getting dates they can trust. You can supply those dates without supplying task-level estimates.

What can you give a client instead of a Gantt chart?

A cycle calendar with fixed start and end dates, the shaped pitch for each cycle and a hill chart during the build. That gives them dates, scope and progress on one page each.