A review with examples of how to effectively communicate the progress of a project using a project storyboard.

1. Section & Lesson #:
Pre-Requisite Lessons:
Complex Tools + Clear Teaching = Powerful Results
Project Storyboard
Introduction – Lesson 10
A review with examples of how to effectively communicate the progress of
a project using a project storyboard.
None
Copyright © 2011-2019 by Matthew J. Hansen. All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted by any means
(electronic, mechanical, photographic, photocopying, recording or otherwise) without prior permission in writing by the author and/or publisher.

2. o What is the project storyboard?
• It’s a document (typically a set of PowerPoint slides) that “tells the story” of the project.
 It generally summarizes the premise, analysis, & results of the project.
 It can be used during the project (for getting team/stakeholder buy-in) or as a post-project reference.
• It often changes throughout the duration of the project.
 Don’t be afraid to add, delete, or modify parts of the storyboard if it enhances the overall project story.
o What method or style should be used for the storyboard?
• There is no official or formal storyboard style.
 Some Lean Six Sigma organizations require a standard storyboard layout.
 If a formal storyboard layout isn’t required, then use what is easiest for you to communicate the story.
• Use the KISS method (Keep It Simple, Stupid).
 Target the language & concepts of the storyboard to a 6th grade level.
 Explain any unique business concepts, terms & acronyms along the way.
– It may be helpful to add a glossary of operational definitions as an appendix to the storyboard.
 Use pictures or charts to help explain key or complex concepts.
– Only use clipart if it’s relevant; if complex statistical tools are necessary, simplify them and use call outs to explain them.
• Use the KILL method (Keep it Logical, Loser).
 The flow of the story should be logical and consistent; if any part doesn’t make sense, then exclude it.
o Storyboard Tips:
• Keep your main points of the story at the front of the storyboard; use the appendix for details.
• Try using a Question: Answer format; this lets the audience know what you’re trying to answer.
• Add an executive summary to front of the storyboard and add a “Takeaway” to each page.
Project Storyboard Defined
Copyright © 2011-2019 by Matthew J. Hansen. All Rights Reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted by any means (electronic, mechanical, photographic,
photocopying, recording or otherwise) without prior permission in writing by the author and/or publisher.
2

3. Project Storyboard Example 1
o Project Example 1: Back Office Processes
• This project had 6 different opportunities that were explored based on using the IPO-FAT tool.
Copyright © 2011-2019 by Matthew J. Hansen. All Rights Reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted by any means (electronic, mechanical, photographic,
photocopying, recording or otherwise) without prior permission in writing by the author and/or publisher.
3
Pg 11 compares an As-Is & To-
Be process map that supports
opportunity #2 (pg 6); it’s
helpful but not critical to the
story ,so it’s in the appendix.
Pg 5 – 10 each summarize one opportunity
(problem, root cause, improvement & results).
Each page also references the IPO-FAT from pg 4
to help the reader follow the project story.
Pg 4 uses the IPO-FAT as a
project strategy with each cell
noting potential opportunities.
Pg 12 is a Control Plan that
covers some of the project
opportunities. It’s critical to
the project but not the story
so it’s added to the appendix.
Pg 3 summarizes the Project
Charter (problem statement,
scope, and team members).
Pg 1 (Cover) included an Exec Summary
and pg 2 had a brief summary about Lean
6Sigma (to introduce the methodology).

4. Project Storyboard Example 2
o Project Example 2: Call Reduction Project
• This project started as a pilot to find ways to significantly reduce call volume at a call center.
Copyright © 2011-2019 by Matthew J. Hansen. All Rights Reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted by any means (electronic, mechanical, photographic,
photocopying, recording or otherwise) without prior permission in writing by the author and/or publisher.
4
Pg 5 summarizes the team’s
recommendations by laying them
out visually as 3 simple steps.
Pg 2 summarizes the Project
Charter (problem statement,
scope, and team members).
Pg 3 - 4 explain the implemented improvements,
their results, and answers other potential questions
the audience may have. The analysis to find the
improvements weren’t critical to the story.
Pg 1 (Cover) included an Exec
Summary.
Call Reduction Project

5. Pg 3 – 6 answer the 3 simple questions in the strategy. They’re depicted visually
using the same pie chart and then layering the subsequent question/answer on
top of each other. This method adds consistency to the story for the audience.
Repeat Caller Alert (RCA) Analysis: Q1 Finding
Project Storyboard Example 3
o Project Example 3: Repeat Caller Alert (RCA) Analysis
• Though this was more of an analysis than a DMAIC project, a storyboard was used to explain it.
Copyright © 2011-2019 by Matthew J. Hansen. All Rights Reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted by any means (electronic, mechanical, photographic,
photocopying, recording or otherwise) without prior permission in writing by the author and/or publisher.
5
Pg 1 (Cover) didn’t have an Exec
Summary; Pg 2 described the problem
and explained the analysis strategy as
answering 3 simple questions.
Repeat Caller Alert (RCA) Analysis: Charter
Repeat Caller Alert (RCA) Analysis: Q1 Finding
Repeat Caller Alert (RCA) Analysis: Q1 Finding
Repeat Caller Alert (RCA) Analysis: Q1 Finding
Based on the results from the
analysis, pg 7 does a Min/Max
analysis to find the opportunity
isn’t worth it (low ROI).
Repeat Caller Alert (RCA) Analysis: Tech Impact
Pg 8 summarizes the analysis
conclusions &recommended
next steps.
Repeat Caller Alert (RCA) Analysis: Conclusion

6. Project Storyboard Example 4
o Project Example 4: Road Empty Miles Project
• This project reflects a more formal and comprehensive storyboard layout.
Copyright © 2011-2019 by Matthew J. Hansen. All Rights Reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted by any means (electronic, mechanical, photographic,
photocopying, recording or otherwise) without prior permission in writing by the author and/or publisher.
6
Pg 1 is the cover page, pg 2 is a table of
contents (since the storyboard was long), and
pg 3 gave a brief summary about Lean 6Sigma.
Pg 4 – 8 included content for the Define phase such as a stakeholder
analysis, project charter, scope definition and high-level process map.
Pg 9 – 11 began the Measure phase content
to explain how a defect was defined and to
size up the potential opportunity.
Pg 12 – 14 explain the method used for finding defects, real examples across the
U.S. of where these defects exist, and a more detailed sizing of potential benefits.
The rest of the project slides are omitted from this example.

7. Practical Application
o What are some examples of project storyboards that you or others have created?
• In what ways were they effective?
• In what ways were they not effective?
• Did the audience respond to the storyboard message as was intended?
 If not, then how could the storyboard have been more effective in communicating to the audience?
o What storyboard tips & techniques would help for your future storyboards?
Copyright © 2011-2019 by Matthew J. Hansen. All Rights Reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted by any means (electronic, mechanical, photographic,
photocopying, recording or otherwise) without prior permission in writing by the author and/or publisher.
7