Professional Documents
Culture Documents
SHOULDBEFACTBOOK
SHOULDBEFACTBOOK
Should Be Factbook
Contact: Jeremy Lagomarsino
March 2000
Copyright© 1998 Bain & Company, Inc.
Should Be Factbook
Agenda
• Objectives
• Objectives
Instructions
• Create story in 5-6 bullets
• Use entire package to drive three
presentations
- 3 minute version (one slide)
- 45 minute version (10-15 slides)
- 3 hour version (40-60 slides)
• 10-15 word • Bullet points written in “proper” English, i.e. full sentences, correct grammar,
summary of each etc.
key section
- Sub Bullet
Sub-sub Bullet
Instructions
• Use 1-3 slides to summarize the entire output of
the redesign phase for your process:
- what has been looked at
- what was broken and needs fixing
- how will it be fixed and what are the key
Critical Actions
- how will the key Critical Actions be
implemented
- what value will they create for the business
• Be as concise, specific, and quantitative as
possible
• Ask yourself “If these were the only slides a senior
executive were to read about our process, what
would we need to include?”
• "As is" provisioning • Telco is forecast to spend approximately $280M ($80M opex, $200 capex) on provisioning
process is high cost of customers on the network over the next 18 months
• The current provisioning process is characterized by:
- high cost per install (opex and capex)
- $1,000 per sub
- lack of proximity of installs - geography and time
- variable cycle times
- lack of coordination between marketing, sales, and installation
- lack of coordination between subscriber service groups
• "Should be": A targeted • The "Should be" vision estimates a significant improvement in the economics of connecting customers by developing a targeted,
neighborhood by neighborhood neighborhood based roll-out of the network:
roll-out of the network
- concentrated node roll-out, and sales and installation process, reduces “non-work” time and facilitates “volume” based
significantly improves the
economics provisioning
Service Provisioning
Respond to Identify Network Confirm Fix Billing
Diagnose
Sales Customer Performance Restore Fix and Update and
and Prioritise Collections
Service Issue Issue Systems
Network Creation
• Providing fully- • Customer service • Real-time surveillance of • Investigation, diagnosis, and • All stages of • All permanent • Updating all • Recording
the Telco network prioritization of problem reports
defined and functionalities temporary repairs relevant call
- collecting information • restoration process, databases for detail data
fully-tested: Performance management • Performance management
- transferring monitoring related to efforts resulting from trending including new
- platforms customers to correct assurance analysis • Coordinate and/or
- diversion of configuration or
- trending analysis
- products location traffic fix Telco
- reporting • Dispatching problems to inventory
- services - resolving questions appropriate work force - temporary fix sold/leased
depletion
and complaints • Maintaining defined service until permanent CPEs/handsets/ST
- basic levels • Escalation of problem fix can be Us
troubleshooting - preventative resolution, if necessary (up to • Closing with the
maintenance 7 stages) addressed
- reporting - change management customer
Instructions
• Create detailed blank diagrams of
process scope with supporting
detail
Providing status
- to customer
- to internal Telco
areas
Instructions
• Create detailed maps of higher level
inputs and outputs
• Carefully document inputs and outputs of
each sub Critical Action in 1-2 slides each
Instructions
• Describe the “As-is”
• The description should be accompanied
by a graphical depiction of the “As is”,
which can be used to compare against a
similar graphical depiction of the “Should
be”
• One or more slides may be used
Identify Translate Prepare Review and Bid and Test and Review/
Prioritize Install
Requirements Requirements Business Case Approve Procure Certify Hand-off
Network: • Forecasting • Unclear • Potentially • Sometimes • Lack of • Vendors not • Full value of • Inconsistent
process is linkage to over- ignore accountab- managed outsourcing record
aggressively
significantly strategy dimensi- operational ility for may not be keeping and
• Some unit costs
broken oning some and support performance and cycle times captured document-
elements of requirements • Some could be • Timing of ation
network • Limited process improved implemen-
flexibility for inefficiencies • Problems in ations may not
logistics lead to
different equipment
be optimal
project types shortages
Instructions
• Use 3-10 slides to summarize the "As-is" economics
• Key elements to include are:
- total cost
- unit cost
- relevant benchmarks
- cost drivers (for each major cost category)
• Examples of suitable slide formats are provided. Those stamped “Template”
are slides which should be replicated for your process in an identical format;
the others are examples provided for reference
• Feel free to include additional slides which are relevant for your process
Mail
$76M $32M $29M $23M $23M Total
100%
Managed Data Processing Staff License
$183 M
Staff Accounts Paper
80%
Vendor Fees
Percent of Total Cost
Print
Support
60%
Mass Vendors
40% Mail
Market
Bad Debt
Operations
20%
Staff
0%
Receivables/Collections Query Bill Payments IT
Processing
Handling Distribution
$1.35
$1.5
$1.22 $1.19 $0.99 • High channel costs
- vendor fees
$0.85
$0.70 - internal processing costs
$1.0
$0.56
$0.5
$0.0
Channel Player E
Channel Player A Channel Channel
Channel Player H
Channel Player G
Channel Player F
Channel Player I
Channel
Player B Player C Player D
Instructions
• Describe customer feedback from surveys
or benchmarking activity
• Address key areas
- service
- price
- reliability
- functionality
Bad Debt
Bad Debt/
BNS Revenue
Drivers
Telco 0.3%
2.5% • No credit screening
• No credit screening
Bad Debt
2.4%
Instructions
• Describe benchmark findings in 1-3 slides
Instructions
• Document the high level vision statement
that provide direction and inspiration (will
incorporate competition imperatives)
• Focus on the “where are we going to be”
rather than “how are we going to get
there”
TODAY
TODAY TOMORROW
TOMORROW
• X employees • Y employees
• Revenue/employee ~$159K • Revenue/employee ~$200K
• 1-2 new products/year • 5-6 new products/year
• 3% of revenue and <1% of margin for • 10% of revenue and 5% margin for
new products new products
• Average duration of a simple new • Average duration of a simple new
connect ~20+ minutes connect ~5 minutes
• 2% of customers using electronic • 20% of customers using electronic
channel for ordering/changing service channel for ordering/changing service
• etc. • etc.
Instructions
• The intention of this slide is to provide a
data-driven summary of the “before” and
“after” picture at the process level by
highlighting key changes from "As is" to
"Should be"
• Each bullet point should have key data
quantifying improvements made
Marketing Strategy
IT
Credit Receivable Bill Query Payment
Product Development Collections
Service Provisioning
Control Identification Distribution Handling Processing
Sales
• Billing involvement • Extend scope of• Establish • Negotiate with • Reduce • Migrate • Risk based
in value proposition credit screening Revenue vendors enquiry customers to collections
development • Improve Assurance • Migrate volumes electronic approach
customers to through clearer
opportunities for team to put in payment • Earlier detection
electronic billing billing formats
credit- place revenue • Optimize bill channels and actioning
challenged • Automated call
leakage control format to handling
• Automated call
customers mechanisms reduce length handling
Instructions
• Describe the "Should be"
• Maintain same format as "As is"
description to enable easy comparison
• The description should be accompanied
by a graphical depiction
• One or more slides may be used
Knowledge
Knowledge
Organization
Organization ITITSystems
Systems Incentive
IncentiveSystems
Systems Management
Management
Ideal • Implemented • Prioritized and • Full alignment of • Well-understood
Future: organizational executed plan to organization mechanism for
structure with establish incentives to capturing ongoing
appropriate job infrastructure promote required learning and
descriptions that necessary to behavior to fulfill cycling it back into
has appropriate support business ideal future the organization
alignment to drive decisions, metrics
business to to reach vision
breakthrough
performance
Slow product rework & Rapid product rework & Process speed
re-release process re-release process gap
High
Carefully consider the Choose the change
Change Campaigns that campaigns that fit in
fit in this quadrant. this quadrant.
Impact
Low
Mixed
Positive Neutral Negative
Impact
Impact Impact Impact
(any mix)
el 1
Le v
el
Le v
5
Note: See Change Campaign Results Readiness Indicator module for more details
Core Process Redesign Toolkit
BOS SHOULDBEFACT 36
BOOK1
Template
Should Be Factbook Should Be Factbook Templates
Change Campaign Summary
Core
CoreProcess
ProcessName
Name
Change Campaign 1 Change Campaign 2 Change Campaign 3 Change Campaign 4
Total
No. of
Critical Actions: X X X X X
Critical Action 1.1 (Name of Critical Action) 2.1 (Name of Critical Action) 3.1 (Name of Critical Action) 4.1 (Name of Critical Action)
1.2 (Name of Critical Action) 2.2 (Name of Critical Action) 3.2 (Name of Critical Action) 4.2 (Name of Critical Action)
1.3 (Name of Critical Action) etc. etc. etc.
etc.
Instructions
• Provide one-page summary of the
redesign components
• Text on this slide should be limited to the
name of each Change Campaign and
Critical Actions (subsequent slides will
provide more details)
Instructions
• As with the "As is" economics section, use 3-10 slides to summarize "Should be"
economics
• Key elements to include are:
- unit cost and total cost impact
- sources of savings
- performance versus benchmarks
- implementation investments
• Examples of suitable slide formats are provided. Those stamped “Template” are slides
which should be replicated for your process in an identical format; the others are
examples provided for reference
• Feel free to include additional slides which are relevant for your process
• Special notes for processes projecting incremental revenue due to "Should be":
- the materials in this pack focus mainly on the cost side. Where revenue benefits are
projected, include additional slides as appropriate
- a revenue version of the following slides should always be included
“Impact on Total Cost” (i.e. Impact on Total Revenue)
“Sources of Savings” (i.e. Sources of Incremental Revenue)
100 100%
Managerial
Other
80 80%
Processing
60 60%
Collections
40 40%
Order
20 20%
entry
0 0%
Should Be
2000
As IS 1999
2001
CC1 1.1 $ $ $ $ $ $ $
Change 1.2 $ $ $ $ $ $ $
Campaign 1.3 $ $ $ $ $ $ $
Name
Total: $ $ $ $ $ $ $
CC2 2.1 $ $ $ $ $ $ $
Change 2.2 $ $ $ $ $ $ $
Campaign 2.3 $ $ $ $ $ $ $
Name
Total: $ $ $ $ $ $ $
CC3 3.1 $ $ $ $ $ $ $
Change 3.2 $ $ $ $ $ $ $
Campaign 3.3 $ $ $ $ $ $ $
Name
Total: $ $ $ $ $ $ $
CC4 4.1 $ $ $ $ $ $ $
Change 4.2 $ $ $ $ $ $ $
Campaign 4.3 $ $ $ $ $ $ $
Name
Total: $ $ $ $ $ $ $
Total: $ $ $ $ $ $ $ $
* Exclude financing cash flows and tax Core Process Redesign Toolkit
Note: Incremental economic impact values include one-time costs; full potential values do not BOS SHOULDBEFACT 41
BOOK1
Template
Should Be Factbook Should Be Factbook Templates
Table of Contents
• Scope
• "As is"
- process overview
- economics
- customer requirements
- competitive benchmarking
• "Should be”
- vision
- process overview
- Change Campaign diagnostic
- economics
- metrics
- organizational requirements
- IT requirements
- other core process dependencies
• Appendix
- glossary of terms
Frequency*
"As is" Sep ‘99 Oct ‘99 Nov ‘99 Dec ‘99 1999
Reporting
Relevant
Data
Actions
Critical
Metrics Source
Level
Date
7 14 21 28 5 12 19 26 2 9 16 23 30 7 14 21 28 Jan Feb Mar Q2 Q3 Q4
FY97/98
W
1.3
240
2.4
Metrics 2 M
Metrics 3 M
Metrics 4 M
Metrics5 W
Metrics 6 W
Target
IT $4.82 Collections
Cost per Bill
60%
$3.95
$4 Billing
57%
Payments
70%
Handling
40%
Query
49%
20%
$2
Bad 17% 20% Bad Debt
Debt
61%
$0 0%
Unit Cost Reduction (to 6/01)
$M
$M
Total Process Cost
$M
$__
$__
Industry
Average
$__
$__
Instructions
• Present “As-is” organization charts for
all major areas impacted by redesign
= Approval
IA= Input en
t
r/
er
/S
I
en
t
D = Decision e m M age
ag em
t g A an n g te
DI = Decide en a /C a r a
= Input m M an ger t in
g
M
M ge an ing er uo
e A M a r r m a M e Q
ag /T ld s
gi ine
e e a e an nd n n & te g
VP Fie an ne gr nc an gi id o rin
A = Approve an s / t M rate Eng tor gi Pro ina s
M
ra t Pl En t B Qu cts tu ip
M le n n t n s /B t c
uc &
c
ne uct duc duc a
d
or Sa ivis
io u S el ire
co ield Fi I D ield Fie
E ld F
si
ra uf Sh
ct el
d od id nt an rop
Se D Ac F S F Fi Bu r od Pro Pro Pr B Co M
Decision P D
Account planning A D D D I I I
Project strategy A A A D D A D D I D A I I I I I I
Influence customer A A A D D A I D D A I I I I D I
Budgetary quote A A D D A D D I D A I I I I I I I
Competitive advantages/strategy A A A D D D I I D A D D D D
System concept A A A D D A D D D A I I I I I
Negotiation strategy A A A D D A I D I I I D
• Highlight level of challenge expected
in moving organization
Contract pricing/Ts & Cs A A A D D A I D D D A I I I I D I D
Instructions
• Develop and present “Should be”
organization chart required to drive
results
Among the project participants, responsibilities and authority are clearly defined. A
core team led by the certified project owner, is responsible for all decisions through
project completion, drawing on support and centralized information as required.
I =I Input
= Input
D =D Decide
= Decision
A =AApprove
= Approval
Decision
Account Planning D I
Project strategy A D I I I I I I
Influence customer A D I I I I I
Budgetary quote D I I I I I I I
Competitive advantages/strategy D I I I I
System concept D I I I I I
System design A I D I I I
Service/SI plan A I I D I I
Negotiation strategy D I I
High
Impact
• Timing
• Performance
Low
Easy Hard
Ease of
implementation Instructions
• Timing • Highlight IT driven dependencies
• Resources
• Category dependencies according to their
required
impact and ease of implementation
Term/Acronym Definition
Instructions
• Provide a summary of relevant terms and
acronyms used in the "Should be" Book