How To Choose The Right First A3 Project

The first A3 project does not need to be the biggest problem in the business.

It needs to be a problem the team can see clearly enough to learn from.

That distinction matters. Teams often begin with a goal that is too broad, too political, or too far outside their control. They call the project “improve customer service,” “reduce waste,” or “fix communication.” Those may be important ambitions, but they are hard to observe, hard to test, and easy to turn into a list of opinions.

A better first A3 starts with one condition that matters to the people doing the work. It is narrow enough to understand, real enough to investigate, and practical enough to test a countermeasure.

1. Start With A Condition You Can Observe

Choose a problem that you can describe with facts, not only frustration.

For example, instead of “our handoffs are poor,” start with a condition such as:

• two of every ten requests are missing required information when they reach the next step;
• the team waits an average of two days for a decision that should take one day;
• the same order error is corrected three times a week;
• the start of the shift loses thirty minutes because materials are not ready.

You do not need perfect data before starting. You do need a way to go and see what is happening now.

If the team cannot describe the current condition, the first task is observation, not a solution meeting.

2. Make The Project Small Enough To Learn From

The best first A3 is usually smaller than people expect.

Pick one process, one product family, one shift, one handoff, or one recurring defect. Avoid taking on the entire department, a multi-year strategy, or every complaint at once.

Small does not mean unimportant. It means the team can see the work, understand its boundaries, and test whether a countermeasure changes the condition.

For example, a team may eventually need to improve all order-entry quality. Its first A3 could focus on the one customer-request field that causes most rework during one shift. That is enough to practice defining a problem, checking facts, tracing a cause, and following up.

3. Choose A Problem The Team Can Influence

Your first project should have a clear owner and a team that can influence the process.

That does not mean the team controls every cause. Real work crosses functions. It means the group can observe the work, talk with the people involved, and test a change without waiting for a major organizational program.

Before choosing the project, ask:

• Who sees this condition regularly?
• Who can help observe the process?
• Who can test a small countermeasure?
• Who will check whether the condition improved?

If no one can answer those questions, choose a smaller project or bring the right people into the first review.

4. Look For A Repeat Problem, Not A One-Time Emergency

A3 is most useful when the team wants to understand and improve a recurring condition.

An emergency may need immediate containment. A first A3 can still begin after that immediate response, when the team asks why the same issue happened and what would prevent it next time.

Good first-project signals include:

• a repeated delay, defect, missed handoff, or rework loop;
• a countermeasure that was completed but did not hold;
• a process that people work around instead of improving;
• recurring questions because the standard is unclear;
• time spent correcting the same avoidable condition.

The project is not “stop every issue forever.” The project is to understand one repeatable condition well enough to test a better way of working.

5. Do Not Choose The Solution Before The Problem

“We need a new checklist” or “we should automate this” may turn out to be good ideas. They are not problem statements.

Start with the current condition and the effect it creates. Then observe the work, ask what is happening, and separate a symptom from a likely cause.

This protects the team from spending its first A3 defending a preferred answer. It also makes the learning more useful: the group practices evidence, not just document completion.

6. Use A Simple First-Project Screen

Before committing, test the candidate against five questions:

1. Can we describe the current condition with an example, count, time, or direct observation?
2. Is the scope small enough to study in the next few weeks?
3. Does the team have an owner and access to the work?
4. Is this a repeat condition rather than a one-time emergency?
5. Could the team test one countermeasure and check what happened?

If most answers are yes, the project is probably a good first A3. If not, narrow the scope. You are not lowering the ambition. You are giving the team a better chance to practice the method well.

7. Choose The Next Step That Fits The Need

If you have one real condition to work on and need help selecting a practical starting point, review First Projects in Your A3.

If you already know the problem and need a structure for the first draft, download the A3 problem-solving template.

If the question is bigger than one project, such as whether a team needs shared A3 practice, leadership coaching, or a broader learning path, take the Team Problem-Solving Skills Assessment.

The first project is not a test of whether the team is already good at A3. It is a safe way to build the habit of seeing the work, checking facts, and following through.