1. R&D
Knowledge Management
Opportunities for Design

2. http://bit.ly/km pulsecheck
Knowledge Management
What? So What? Now What?
Definition
Importance
Measuring – Pulse Check
pulsecheck
Eric: (15 mins)
What is knowledge management? Why is it important?
Overview of the KM Pulse Check
Have everyone complete the pulse check
Results will be in Monday’s Burst
Next pulse check will be in six weeks

3. 2 – 4 – 6 Number Sequence Pairs Activity
We have a rule for generating number sequences. Here is an example of one number sequence that “conforms” to the rule.
You have Number Sequence Test Cycle Tracker worksheets on your tables.

4. Record the results of the test
Write your most current theory of what the rule might be
Write the sequence you’d like to test this cycle
Indicate your prediction about the sequence
With a partner, generate sequences that you think conform to the rule
For each cycle:
• Hypothesize a rule.
• Write down a specific sequence to test.
• Predict whether you think the sequence will conform to our rule or not.
• Raise your hands to call over a facilitator, who will then classify the tested sequence as either conforming or nonconforming to our rule.
• Record the results of your test.
Run as many cycles as required until you are sure you know the rule, then record your final rule at the bottom of the page.
RULE: any three numbers (positive integers) in ascending order

5. Plan – Do – Study – Act A P D S How many test cycles did you complete?
Debriefing the Number Sequence Activity and Connecting to PDSA
How many test cycles did you complete?
In which cycle(s) did you experience the most valuable learning?
Did you identify the correct rule?
How does this activity model PDSA cycles? A P D S
P = Theory  Hypothesis
D = Try
S = Check, compare results to predictions, reflect on results
A = Learn, adapt theory, next cycle

6. PDSA Cycle Act Plan Do Study Try Collect data Document Observations
Compare results to predictions
Reflect on learning
Research
Theory
Hypothesis (Prediction)
Adjust
Document learning
Next cycle
Act
Plan Do
Study
Simplified version – of course, plan phase also includes planning to execute on D-S-A phases.
Act: includes knowledge management – at some point, may determine that it’s time to abandon (idea is to know this quickly, before investing and wasting too much time, energy and money)

7. Learning and Improvement
PDSA Ramps
“Quality with Reliability at Scale” A P D S
Data and Evidence A P D S
Wider-scale Tests A P D S
Follow up Tests
Learning and Improvement
Otherwise, keep building on learning each cycle, increasing size of test over time – e.g., an innovation might begin with one or two coaches with one or two teachers each through several cycles, then as refined, these coaches may expand the number the number of teachers, then the number of coaches – don’t get to quality by jumping to scale.
ITERATION is the key – once you’ve completed a PDSA cycle, not done. Part of Act phase is planning the next cycle, based on learning from the previous cycle. May not be in immediate succession, may not be same players  importance of knowledge management to ensure continuously building on learning.
Just because it “works,” doesn’t mean you’re done – could we do it better, more efficiently, less expensively?
Break large projects into smaller cycles, roughly 90 days each.
e.g., KM Pulse Check – in first iteration, completed Planning, about to Do, will Study, then Act; similarly with the design you’re about to see
Theories, Hunches, Promising Practices
Small-scale Tests

8. Opportunities for Design
Grouped by Dreams and Gripes Themes
May Core Team – “Pre-cycle”
PLAN – May to June
2-2-1:
2 research articles
2 interviews
1 out-of-the-box approach
 How will your team share what you learn?
DO – June to July
Try something!
Test
Collect data
Try something else…
Touch base as a team to share what you’re learning, iterate on design, and prepare to Study
Decide on topic – if a really complex issue, focus on something the team can tackle in a few months
Pre-cycle template (digital): Intent, aim, audience, deliverable, team, key resources and experts? – we will put this through PDSA cycles between now and May, as well as digital collaboration space
PLAN:
Don’t get mired down in planning – “admiring the problem”
What are the stakes? (How much to lose if you get it wrong?)
The less the potential harm, the shorter the researching and planning!
Aim: sufficient to prototype a framework, process, tool or new practice – not meant to be exhaustive, or even comprehensive
DO:
Multiple, rapid, SMALL tests – in theory (peer/expert review) or practice

9. Opportunities for Design
Grouped by Dreams and Gripes Themes
STUDY – July to August
Examine collective data
Compare results to predictions
Make meaning
Additional, more focused trials as needed
Summarize learning
ACT – Core Team Retreat
Share:
Intent
Background
Process
Results
Conclusions and Recommendations
“Pre-cycle” for next PDSA
Will be working on tools to support this work between now and May.
Will reach out to some folks about leading a team, but if you know you’re interested, let us know.
Will also work with leadership to ensure time for PDSA work.
Will pull team leads together before May Core Team to prep.
General format: “Pre-cycle in Core Team, Plan and Do between Core Team meetings, pull up to study/reflect together at next Core Team meeting, Do and Study between Core Team meetings, then Act at next Core Team  launch next PDSA wave with pre-cycle
 4-month cycles three times a year