Platform Development Charters: Setting the Stage for Platform Development

Key Takeaways:

  • Product Platform Architectures eliminate waste along the entire value stream.
  • Levels of modularity allow a company to adopt a Platform Architecture strategy that
    fits their industry, product strategy and customer needs even in situations with high demands for tightly integrated product designs.
  • Platform architecture teams require clear strategic objectives to guide their decisions.

More Details:


Author: 
Katherine Radeka
Created: 
September 8th, 2008
Updated: 
March 20th, 2012
Anatomy of an A3 Report: Focusing Knowledge for Better Decision-making

Key Takeways:

  • A3 reports present the essential information about one focused subject on a single large sheet of paper, using visual models to deepen shared understanding.
  • Three types of A3 reports share some standard elements but allow for flexibility.
  • The A3 format is highly versatile so long as documents follow the principles of focus, brevity
    and visual models.

More Details:


Author: 
Katherine Radeka
Created: 
September 8th, 2008
Updated: 
September 8th, 2008

This is an example of a Documentation Replacement A3. It replaces a Feature Request document by summarizing the key information on a single A3 report.

More Details:


Author: 
Katherine Radeka
Created: 
March 18th, 2012
Updated: 
March 18th, 2012

This is an example of a Status Report A3.

More Details:


Author: 
Katherine Radeka
Created: 
March 18th, 2012
Updated: 
March 18th, 2012
Find The Knowledge Gaps: How to Capture the “Known Unknowns” and Find the “Unknown Unknowns”

Key Takeaways:

  • Almost all product development programs seek to close knowledge gaps.
  • We are more likely to find the critical knowledge gaps when we ask questions from a variety of different angles and perspectives.
  • An inventory of knowledge gaps helps us assess the maturity of our product designs, and understand the amount of risk we’re carrying into late development.

More Details:


Author: 
Katherine Radeka
Created: 
January 6th, 2012
Updated: 
January 6th, 2012
A Checklist for Designing a Checklist: How to Design Checklists That Get Checked

Key Takeaways:

  • Checklists are a useful tool for preventing mistakes - when they get used.
  • Product developers respond especially poorly to externally-imposed checklists, but respond well to the requirement to develop their own.
  • Good checklists are short, focused on the critical few, and designed to support judgement rather than replace it.

More Details:


Author: 
Katherine Radeka
Created: 
September 29th, 2011
Updated: 
September 29th, 2011
Areas of Excellence: The Discipline of Focused Innovation

Key Takeaways:

  • Spheres of Excellence help an organization decide where it will focus its innovation to define the organization’s IS - IS NOT boundaries.
  • Attempting to be Breakthrough at everything is very expensive and usually not effective or necessary. Instead, we should focus on the areas that will help us become the organization we want to be.
  • Inertia causes our spheres of excellence to lose their competitiveness over time.

More Details:


Author: 
Katherine Radeka
Created: 
April 26th, 2010
Updated: 
April 26th, 2010
How to Convert a Project-Specific A3 into Reusable Knowledge

Key Takeaways:

  • The fastest way to begin building a library of reusable knowledge is to become skilled at converting Problem-Solving and Proposal A3s into Knowledge Capture A3s.
  • Most of the sections of the original A3 will just need to be updated to reflect the current state of the implementation.
  • The author will add sections to capture lessons learned and make actionable recommendations to help the next reader apply them.

More Details:


Author: 
Katherine Radeka
Created: 
February 17th, 2011
Updated: 
February 17th, 2011
Tacit Knowledge: When Documentation Is Not Enough

Key Takeaways:

  • Poorly-written documentation does not transfer knowledge because it is not well-understood, believed or actionable. At best, such documents provide information.
  • Even the best documentation cannot communicate everything that a person needs to know because tacit knowledge does not lend itself to documentation.
  • Externalization, guided experiences and reflection help transfer tacit knowledge.

More Details:


Author: 
Katherine Radeka
Created: 
June 29th, 2010
Updated: 
June 29th, 2010
Knowledge Capture Interviews: Externalize Your Most Valuable Technical Knowledge with Pull

Key Takeaways:

  • Tacit knowledge is easier to turn into explicit knowledge if something is pulling.
  • Knowledge Capture Interviews benefit the senior engineer, the junior engineer and the organization by driving the process of externalization with pull.
  • It is less important to choose the best topics for Knowledge Capture Interviews than it is to pick a topic for the first one and then carry it all the way through to completion.

More Details:


Author: 
Katherine Radeka
Created: 
June 22nd, 2010
Updated: 
June 22nd, 2010