In the world of process and process improvement, it is important to be realistic about what is actually possible. Constraints often prevent us from designing the process of our dreams. In this meetup we discussed what a constraint is in the context of business process optimization, how to identify them by using creative design activities, and how these imaginative exercises can be practically applied for realistic process improvement.

1. Constraints and Blue Sky Design: The Role of
Imagination in Process Design
NYBPP Meetup (11/22/2017)
Highlights and Q&A

2. Agenda
I. Constraints and Blue Sky Design: The Role of Imagination in Process
Design
■ “Blue Sky” Brainstorming
■ Understanding Constraints
■ Focus your Design: Doing the As-is Better
■ Add Back the Constraints
■ Summary
II. Q&A
■ Shouldn’t you just ask stakeholders what the value is first instead of researching
the workflow?
■ Who defines value? isn’t it subjective?
■ Isn’t it a waste to design without known “fatal” or unchangeable constraints?
■ How often should you do process improvement?

3. Constraints and Blue Sky Design: The
Role of Imagination in Process Design
Guiding design thinking to align with the value chain

4. “Blue Sky” Brainstorming
A way of brainstorming without typical restrictions
1. Without any obstacles, what is the most efficient way
this process could function to deliver value to our
client?
2. How can we immediately fix the pain points or
problems we have identified (we don’t need to get
specific)
3. Use your imagination in terms of designing new
technology or erasing existing barriers “magic wand”
style

5. Understanding
Constraints
A constraint is a limiting
factor that prevents a process
from reaching its entitlement
(perfect performance) state.

6. Understanding Constraints
There are 4 major categories of constraints:
● Physical: The physical limits imposed on processes due to their overall
chemical or mechanical nature
● People: Lack of skilled people limits the system. Mental models held by
people can cause behavior that becomes a constraint
● Policy: A written or unwritten policy prevents the system from
performing optimally
● Project: the project management triangle (scope, cost, and time) in
which you find yourself doing process work.
Sometimes constraints can be removed and sometimes they can’t;
either way, one must know the factors that are preventing a process
from reaching entitlement in order to improve it close to that point.

7. Focus your Design: Doing the As-Is Better
Always start from an accurate as-is process.
No matter how “bad” it is, it is producing value and we’re always
optimizing to value! The exercise is to create the value being created
in the as-is in the most efficient, lowest cost imaginable.
Blue Sky Design

8. Add Back the Constraints
Once you have your blue sky design, bring back the constraints.
This is the time to discuss the minimum design changes needed for the
process to be viable, given the new requirements. Make sure to only
consider the constraints that can’t be removed!
The result should be the ideal, realistic solution.

9. Summary
• Blue Sky design removes constraints and moves focus to the
value chain instead of dealing with symptoms or obstacles.
• To ignore constraints, first identify them. There are four types:
Physical, People, Policy, and Project. Once identified, move
them out of mind for the design phase.
• Always design around making the as-is better. If you don’t
have the right starting point, even blue sky thinking won’t help
you.
• Once you’re finished with design, add the unremovable
constraints back and finish the realistic design!

10. Q&A
Answering questions from the Meetup

11. Shouldn’t you just ask stakeholders what the value
is first instead of researching the workflow?
No, typically stakeholders/SMEs don’t
know the process value from their
perspective.
● The value chain can only be accurately derived from
understanding the process overall. No single individual has that
view point.
● If you ask anyone, they will try to explain the value they produce,
instead of the process overall.

12. Who defines value? Isn’t it subjective?
Value is defined by the market/
environment.
It is inherent - nobody defines it.
Value is subjective from the individual perspective, but not from
the process perspective.

13. Isn’t it a waste to design without known “fatal” or
unchangeable constraints?
No!
● The exercise makes sure that everyone focuses strictly on
value production (because no other obstacles are in the
way).
● Once you come up with something, no matter how
outlandish, work backwards into realistic constraints.

14. How often should you do process
design/improvement?
As often as is cost effective!
● Doing project work (process analysis, design, and
enablement) costs resources and time.
● If every time you do a project, there is positive ROI, you can
keep doing them as fast and often as that remains true.

15. THANK YOU FOR COMING!
• Thank you so much for coming to our meetup – we hope to see you again
in future sessions and please don’t hesitate to post additional questions on
the group discussion board.
NYBPP Meetup
Please leave us a positive review!
• You can view all of our past slides over on Slideshare.net:
Slide Decks from Past Meetups
• Also, join our Facebook Group!
NYBPP Meetup Facebook Group