Chronology of Pflogging web site content

04/01/2004 - 10:16
Transforming knowledge and vision into action
04/06/2004 - 22:55
The nature of the 'unprecedented' beast
04/10/2004 - 11:29
Leveraging the real-time flow of information, resources, and knowledge with automation
04/12/2004 - 10:30
Slaying the beast
04/12/2004 - 10:55
Case studies
04/14/2004 - 19:29
Entertaining the beast
04/30/2004 - 08:21
It's not the tool, it's how you use it: a new business model for delivery of information systems
05/01/2004 - 14:49
Challenges and strategies for community-based development
05/03/2004 - 09:43
Actively manage uncertainty
05/18/2004 - 09:47
Terrain situational awareness and organizational transformation
05/20/2004 - 07:10
Courage, trust, and understanding in competitive estimating
05/20/2004 - 07:57
Your mileage may vary
05/23/2004 - 21:16
Summary of recommendations
05/23/2004 - 21:18
Background
05/23/2004 - 21:22
Governance architecture usage scenarios and needs
05/23/2004 - 21:26
Governance frames of reference
05/23/2004 - 21:29
Implementation dynamics
05/23/2004 - 21:31
Improvement strategies and success factors
06/01/2004 - 14:33
Risk management criteria
06/06/2004 - 17:55
Unavoidable tensions between structure and autonomy: the cultural challenge
06/10/2004 - 11:13
Use of copyrighted material on this site
06/16/2004 - 09:53
Counting code and cows
11/29/2006 - 05:42
Retrospective Risk Management and the war in Iraq
01/05/2007 - 23:41
When a best practice is not good enough
01/05/2007 - 23:42
What are best practices?
01/05/2007 - 23:44
Are best practices always the right thing to do?
01/05/2007 - 23:55
Where does one find best practices?
01/06/2007 - 00:01
Design issues for best practice improvement frameworks
01/06/2007 - 05:02
Governing chaos: getting a grip on policies, processes, and behaviors
01/06/2007 - 05:37
A simple '5 Cs' checklist for reviewing requirements and other written material
01/06/2007 - 05:48
Project management rules of thumb
01/07/2007 - 08:45
Business process framework
01/07/2007 - 22:56
Another candidate project - generic process framework
01/07/2007 - 22:58
Another candidate project - collaboration technologies
01/07/2007 - 23:08
Another candidate project - integration of process improvement frameworks
01/11/2007 - 09:29
Technical process framework
01/11/2007 - 09:33
Manage programs, projects, and product lines
01/11/2007 - 09:35
Perform research and technology development
01/11/2007 - 09:37
Evolve architectures and product lines
01/11/2007 - 09:40
Operate systems
01/11/2007 - 09:42
Perform development and test
01/12/2007 - 00:39
Fragile creations and the decisions that produced them
01/12/2007 - 00:49
Envisioning, evaluating and evolving projects into a managable portfolio
01/12/2007 - 00:51
Why projects fail
01/12/2007 - 00:51
The role of the project leader
01/12/2007 - 01:02
Peeling the systems onion
01/14/2007 - 19:43
Process improvement implementation
01/17/2007 - 07:41
Answers to all your questions
01/17/2007 - 20:41
How to burn down problems before they burn you
01/18/2007 - 05:33
What is an ecosystem, anyway?
01/18/2007 - 05:36
The economics of user-generated content
01/20/2007 - 10:17
Re-imagine!
01/20/2007 - 18:27
The Innocent Man
01/22/2007 - 04:00
Getting things done
01/22/2007 - 06:59
A failure to communicate
01/22/2007 - 08:53
What we know
01/22/2007 - 15:03
The parable of the non-starting car
01/23/2007 - 20:00
Pflogging strategies
01/24/2007 - 06:48
The abc's of behavior
01/25/2007 - 19:25
Having fun with problems
01/26/2007 - 19:43
Inviting Disaster
01/26/2007 - 20:29
Thinking about Systems
01/26/2007 - 20:49
Unknown unknowns
01/26/2007 - 21:12
Overcommitment
01/26/2007 - 22:02
Governance Framework Concepts
01/26/2007 - 22:23
A proper requirements foundation for good governance
01/27/2007 - 07:15
Half of your people are below average and don't know it
01/27/2007 - 11:58
Habits you won't want to break
01/27/2007 - 12:56
Predictions of a radically different future
01/28/2007 - 03:36
Let the blind see
01/28/2007 - 03:59
Are you certain?
01/28/2007 - 04:11
Secrets are scary
01/28/2007 - 04:36
Flight 2.0
01/28/2007 - 09:17
Insurance for project hazards
01/28/2007 - 10:32
Schedule is a monarch, but cannot be a dictator
01/28/2007 - 10:42
Only a software problem
01/28/2007 - 10:52
Systems do not follow a mechanical mental model
01/31/2007 - 04:49
Synergy and collaboration
01/31/2007 - 04:54
The power of one
01/31/2007 - 05:51
The platform idea
02/03/2007 - 01:39
Engineers do not lead normal lives
02/11/2007 - 11:56
Goals vs needs
02/11/2007 - 15:32
How the mind works
02/11/2007 - 15:50
Breakthroughs in visual recognition
02/13/2007 - 04:46
The danger of oversimplification
02/13/2007 - 05:13
Distractability
02/14/2007 - 02:30
What should you be worried about?
02/14/2007 - 20:22
Risky business
02/18/2007 - 09:53
Negative synergy
02/18/2007 - 10:05
Evidence demands a verdict
02/18/2007 - 13:34
Copying mindsets
02/18/2007 - 13:41
Pfeffer's law
02/18/2007 - 13:44
Wisdom and knowledge
02/18/2007 - 13:55
Information socialism
02/20/2007 - 22:06
Design as a repeatable process
02/20/2007 - 22:09
The danger of best practices
02/20/2007 - 23:14
Testing for good rather than for evil
02/25/2007 - 12:58
Changing the autopilot... a journey of self-discovery
02/25/2007 - 13:14
Putting together puzzles
02/25/2007 - 16:15
Natural laws trump heart-felt beliefs
02/25/2007 - 20:28
Trying to be happy
02/26/2007 - 02:44
The more things change, the more they stay the same
02/27/2007 - 06:31
Deploy and utilize tracking systems based upon facts and data
02/27/2007 - 13:20
Stabilize the platform(s)
02/27/2007 - 13:27
Focus action on the critical functionality
02/27/2007 - 13:35
Manage verification discoveries, asset utilization, and yield to achieve required coverage
03/05/2007 - 05:46
Create and maintain a roadmap to provide direction for the team
03/05/2007 - 06:49
Utilize an accountability system to review progress and tune strategies
03/05/2007 - 09:04
Reading minds
03/05/2007 - 10:20
Perhaps it's best to not have a head...
03/05/2007 - 10:26
Open up or die!
03/05/2007 - 14:36
Verification and validation concepts, strategies, and limitations
03/05/2007 - 18:22
No one is perfect
03/05/2007 - 19:11
Failure is an option
03/08/2007 - 19:43
Establish the commitments
03/11/2007 - 09:46
Manage the flow of parts and information
03/11/2007 - 13:14
Navigating without a map
03/13/2007 - 05:05
The code isn't complete until it's engineered
03/13/2007 - 05:27
The best are even better than you think
03/13/2007 - 05:54
How much code can a woodchuck chuck?
03/13/2007 - 07:06
How different is the knowledge worker?
03/15/2007 - 19:35
Borrowing from the future
03/17/2007 - 11:45
Applying lean practices to product development
03/17/2007 - 11:49
What is there to learn from building cars?
03/17/2007 - 12:00
The organization as a system
03/17/2007 - 14:17
Haste makes waste
03/17/2007 - 16:08
Modeling a complex world
03/17/2007 - 18:58
Get branded!
03/19/2007 - 04:08
Geeks and Geezers
03/19/2007 - 04:15
What is experience worth?
03/20/2007 - 06:06
Protocols are better than processes
04/07/2007 - 08:46
Create and acquire new business
04/07/2007 - 08:48
Manage the business
04/07/2007 - 08:51
Manage the supply chain
04/07/2007 - 08:54
Support the business
04/08/2007 - 19:23
We've got upgrades!
04/13/2007 - 16:48
How are best practices best implemented?
04/13/2007 - 16:52
Risk management process example
04/14/2007 - 16:50
Governance lexicon and context
04/14/2007 - 21:44
A checklist for integration risks
04/15/2007 - 15:19
How good is that performance - really?
04/15/2007 - 15:23
It doesn't always pay to be an optimist
04/15/2007 - 15:30
Predicting the future
04/15/2007 - 19:49
Is that a hairball in my corporate soup?
04/15/2007 - 19:55
Catalyzing creativity
04/15/2007 - 20:21
Yet Another Process Maturity Model?
04/16/2007 - 03:37
Just execute!
04/16/2007 - 03:58
The path to effective leadership runs through execution
04/16/2007 - 04:01
When all the plans, processes, and resources are in place, you still have to execute!
04/16/2007 - 04:10
On decision-making
04/16/2007 - 04:20
The secret of success
04/16/2007 - 04:40
The profession of software engineering
04/16/2007 - 05:09
Engineering as a profession
04/26/2007 - 20:05
A treasure box of requirements best practices (and many others, too!)
04/30/2007 - 06:18
Project fire-fighting
04/30/2007 - 06:59
Project Death Marches
05/01/2007 - 16:25
Doctor, doctor, give me the news; I've got a bad case of project blues
05/01/2007 - 19:00
Which hat are you wearing?
05/01/2007 - 22:27
Why the 80 / 20 rule doesn't always apply anymore
05/02/2007 - 03:53
Survival is only an option
05/02/2007 - 04:02
When will it end?
05/12/2007 - 08:04
Consistently improving process performance
05/13/2007 - 18:06
Finding news worth reading
05/15/2007 - 20:24
Shift Happens
05/28/2007 - 05:39
CATWOEs set a nice context for SWOTs
06/14/2007 - 22:58
Walk in the stakeholder's shoes
06/15/2007 - 06:58
Ten questions to discern the real value of processes in a business
06/19/2007 - 05:37
Manage quality before it manages you
06/19/2007 - 05:49
What bug?
06/19/2007 - 20:30
No fear
06/24/2007 - 19:17
On names in general... and Pflogging in particular
07/08/2007 - 08:05
Life in a startup often operates in a different dimension
07/08/2007 - 08:45
Form a Chronic Issue Troubleshooting Team
07/12/2007 - 19:37
What works from an end user's perspective when introducing new products
07/12/2007 - 19:40
What doesn't work from an end user's perspective when introducing new products
07/12/2007 - 19:42
Delivering product support that will thrill your launch customers and save you money
07/14/2007 - 11:03
Ten steps to Innovation
07/15/2007 - 11:36
Why integration hurts
07/15/2007 - 11:41
What makes Drupal work?
07/15/2007 - 12:19
Case study: Adopting a common technology
07/21/2007 - 09:58
Policies drive mechanisms - but not very far!
07/21/2007 - 12:06
Handling product introductions with care
07/22/2007 - 12:03
Leadership pitfalls - success is fickle!
07/25/2007 - 00:00
Collaborative development of processes
07/25/2007 - 19:49
Synergy and natural laws
08/01/2007 - 04:57
Launching teams for sprints to an objective
08/17/2007 - 07:16
How many requirements are enough?
08/17/2007 - 20:48
Why is common sense so uncommon?
08/26/2007 - 06:57
Why is testing software different than testing mechanical devices?
08/26/2007 - 07:01
Why do we test?
08/26/2007 - 07:07
What different kinds of tests do we do?
08/26/2007 - 07:13
How does software fail?
08/26/2007 - 07:21
For further reading...
08/26/2007 - 08:27
How should we then build?
09/01/2007 - 07:19
What exactly does having a 'requirements problem' mean?
09/15/2007 - 09:43
Decision-making through critical thinking
09/18/2007 - 07:01
Knowing what to ask for
09/25/2007 - 20:23
On effective communications
10/05/2007 - 13:17
Mental models
10/06/2007 - 09:24
Case study: Standardizing on a tool
10/06/2007 - 09:28
Case study: Collectively focusing on big, hairy, audacious goals
10/07/2007 - 21:14
My configuration
10/07/2007 - 21:17
The upgrade experience
10/07/2007 - 21:19
The problems begin
10/07/2007 - 21:21
The problems continue
10/07/2007 - 21:23
The relentless pursuit of problem isolation
10/09/2007 - 00:26
Re-thinking the problem
10/13/2007 - 19:44
Troubleshooting 101
10/15/2007 - 03:28
Discipline, risk management, and attention disorders
10/20/2007 - 10:09
On the path to the Matrix
10/20/2007 - 15:08
Catalyzing collaboration
10/21/2007 - 11:46
How does one learn a lesson?
10/21/2007 - 12:11
Normal accidents
10/21/2007 - 16:59
Creating memorable ideas
10/21/2007 - 20:06
Commander's intent
10/23/2007 - 21:02
The genesis of the process revolution
10/23/2007 - 21:34
Unconventional learning
11/03/2007 - 10:38
Managing flow
11/04/2007 - 05:49
Your new methodology - an owner's manual
11/04/2007 - 07:31
Managing quality, deliveries, and priorities
11/04/2007 - 12:39
It's the consequence of a failure, not the failure itself, that matters
11/04/2007 - 18:01
Reinventing Project Management: The Diamond Approach to Successful Growth & Innovation
11/04/2007 - 18:20
Balancing Agility and Discipline: A Guide for the Perplexed
11/04/2007 - 18:26
Lean Software Development: An Agile Toolkit for Software Development Managers
11/04/2007 - 19:49
Putting engineering on a diet
11/20/2007 - 10:04
Making risk management personal
11/20/2007 - 10:59
Keeping the customer happy
11/20/2007 - 11:15
My Vista horror story
11/21/2007 - 16:13
The path to competency
11/22/2007 - 09:43
Pursuing a meaningful definition of competency
11/22/2007 - 18:43
The refuge of scoundrels
11/22/2007 - 18:55
On concensus
11/23/2007 - 13:17
Spacing out
11/24/2007 - 12:08
Holes in both feet are reminders to check the gun isn't loaded
12/04/2007 - 08:20
Management innovation
12/04/2007 - 08:47
Managing people, not things
12/04/2007 - 08:49
It's not just about software
12/04/2007 - 08:51
Talent search
12/06/2007 - 10:27
The hierarchy of human capabilities
12/06/2007 - 14:18
Sustainable successes require management innovation
12/06/2007 - 15:01
Toyota's real advantage
12/06/2007 - 15:03
Denial is not just a river in Egypt
12/06/2007 - 15:07
Slackers reconsidered
12/06/2007 - 15:24
The Internet as archetype for a new management system
12/06/2007 - 16:18
The pain of predictability
12/06/2007 - 16:21
Markets vs hierarchies
12/06/2007 - 16:25
Pay for performance
12/06/2007 - 16:29
Amplifiers of human capability
12/06/2007 - 16:33
Authentic ends
12/06/2007 - 16:36
Preserving humanity in businesses
12/06/2007 - 21:43
The performance review bottleneck
12/06/2007 - 21:47
Reviews and stress
12/06/2007 - 21:52
The risk of honest reviews
12/06/2007 - 21:58
You can't win with measuring people
12/06/2007 - 22:02
The software cost equation is different
12/15/2007 - 09:23
What does it take to achieve consistent outcomes?
12/26/2007 - 08:12
A mental model of job performance
12/26/2007 - 08:31
Key design parameters of a motivational system to accelerate change
12/26/2007 - 08:40
Managing the value of your work: levels of responsibility and authority in assignments
12/26/2007 - 08:42
Factoring in learning and experience - Capacity + Capability
12/26/2007 - 08:55
Identifying opportunities for developing effectiveness
12/26/2007 - 09:04
Monetizing accomplishments and improvements in performance
12/26/2007 - 09:10
The pool of funds for distribution
12/26/2007 - 09:32
Enhancing future performance and job satisfaction
12/26/2007 - 10:00
Lifecycle of an assignment
12/26/2007 - 10:20
Implementation - communicating status and tuning performance through periodic check-ins
12/26/2007 - 10:24
Key performance appraisal customer satisfaction elements
12/26/2007 - 10:30
The performance management close-out review: recognizing accomplishments
12/26/2007 - 10:46
Joining the revolution...
12/27/2007 - 13:57
Measuring the value of an individual's contributions
12/29/2007 - 12:25
The pursuit of pay for performance
12/29/2007 - 12:39
The effect of teamwork and competition
12/29/2007 - 12:52
The path to increased job satisfaction
12/29/2007 - 14:47
Cutting through the fog
12/30/2007 - 10:10
Cast your nets wide
01/01/2008 - 09:47
Principles Of Software Engineering Management
01/01/2008 - 09:50
Replacing production with reproduction
01/01/2008 - 09:54
Like communications, the problem with intelligence is the illusion that it exists...
01/03/2008 - 18:03
Program management information architecture
01/04/2008 - 16:52
Individual salary decisions
01/08/2008 - 19:37
Systematic improvement
01/13/2008 - 09:09
Refining behaviors through personal discipline
01/13/2008 - 09:24
Coaching when you can't do it yourself
01/14/2008 - 07:19
Luck matters
01/21/2008 - 01:03
Goal setting and planning
01/26/2008 - 11:28
Kindergarten 101
01/26/2008 - 11:58
We are what we eat and how it is produced
02/02/2008 - 08:14
The outer motivational loop
02/02/2008 - 09:48
Following the money
02/02/2008 - 10:31
Changing the rules
02/02/2008 - 10:51
On enhancing throughput
02/03/2008 - 10:20
Deconstructing messes
02/03/2008 - 11:01
Feedback
02/03/2008 - 11:04
Side effects
02/03/2008 - 14:44
Counter-intuitiveness
02/05/2008 - 06:58
The culture constraint
02/05/2008 - 07:02
Interdependence
02/05/2008 - 07:05
Systems thinking
02/05/2008 - 07:06
The designer's dilemmas
02/05/2008 - 07:09
The system boundary
02/05/2008 - 07:11
What understanding means
02/05/2008 - 07:15
What is success
02/07/2008 - 07:14
The inner motivational loop
02/07/2008 - 07:21
Interactions
02/09/2008 - 08:43
Best practice risk
02/09/2008 - 09:18
Playbooks and fishing lessons, instead of more laws and sermons
02/09/2008 - 11:29
Failures of confidence
02/09/2008 - 11:52
Failures of perception
02/10/2008 - 14:06
Chronology of a failed quest
02/10/2008 - 14:11
Studying nonzeroness
02/10/2008 - 18:44
Stifling doubts
02/10/2008 - 18:49
Flawed understanding
02/10/2008 - 18:52
Who to trust
02/16/2008 - 07:23
The overhead of switching contexts
02/19/2008 - 06:20
Systems thinking 101: interactions and dynamics
02/29/2008 - 17:16
The talent behind America's game
03/04/2008 - 08:08
The blind side
03/05/2008 - 06:49
The predictable flaws in judgement and decision-making
03/06/2008 - 06:22
Personal mastery
03/06/2008 - 06:33
Copying best practices
03/06/2008 - 07:18
Enabling convergence
03/07/2008 - 10:47
The risk of not changing
03/08/2008 - 08:10
Passion and new knowledge beats old knowledge
03/09/2008 - 16:23
Evaluating and enhancing personal performance
03/15/2008 - 12:03
Assessing the maturity of a risk assessment effort
03/15/2008 - 12:09
Recognizing the learning patterns in medical practice
03/19/2008 - 07:46
The luck of the draw
03/19/2008 - 08:01
Psychology of judgement and decision making
03/19/2008 - 11:21
The inevitability of failure
03/19/2008 - 11:23
Changing the World
03/19/2008 - 11:35
Action orientation
03/19/2008 - 11:40
The proof is in the drilling
03/19/2008 - 11:42
Survival of the willing
03/19/2008 - 11:46
Wealth generation
03/19/2008 - 13:02
Five myths of changing behavior
03/19/2008 - 13:04
Revolutions vs evolutions
03/19/2008 - 13:10
Cultural change
03/19/2008 - 13:12
Reaching
03/19/2008 - 13:18
Cleanliness next to godliness
03/22/2008 - 17:17
We all need a hero
03/24/2008 - 06:55
It's only about survival
03/24/2008 - 07:31
The emotional rollercoaster
03/27/2008 - 06:44
The risks of risk management
03/27/2008 - 22:21
Want to bet?
03/29/2008 - 07:16
Show me the numbers!
03/29/2008 - 12:57
Why most things fail
03/29/2008 - 13:46
Seven deadly organizational sins and their penance
04/02/2008 - 02:50
That's why they call it work
04/07/2008 - 05:13
The physics of us
04/07/2008 - 05:19
Predestination
04/09/2008 - 07:20
The truth is out there
04/11/2008 - 02:37
The opportunities and risks of leadership
04/12/2008 - 07:26
You want it by when?
04/12/2008 - 07:31
Frentic enthusiasm
04/12/2008 - 07:39
Keeping things wired
04/12/2008 - 07:42
Breaking up the work
04/12/2008 - 07:46
The lessons of history
04/12/2008 - 07:49
The biases of software engineering
04/12/2008 - 07:51
Titles, roles, and responsibilities
04/12/2008 - 07:56
Dealing in abstractions
04/12/2008 - 08:00
On reuse
04/12/2008 - 08:05
Integrated performance
04/12/2008 - 08:08
Measuring productivity
04/12/2008 - 08:10
Programming culture
04/12/2008 - 08:14
Tool-making
04/12/2008 - 08:20
What is work?
04/12/2008 - 08:26
Taking responsibility
04/12/2008 - 08:32
The entitlement mentality
04/17/2008 - 05:07
The thought processes behind healing the sick
04/24/2008 - 06:32
What costs to control and when
04/30/2008 - 10:14
Medical robotics
04/30/2008 - 10:16
Architecting solutions
04/30/2008 - 10:22
The practice of software architecture
04/30/2008 - 10:28
How to document Software Architectures
04/30/2008 - 19:44
Evaluating Software Architectures
05/08/2008 - 19:23
Stakeholder perspectives: an interrelated collection of problems and constraints
05/08/2008 - 19:26
Understanding the big picture
05/08/2008 - 19:29
Isolating normal and special cases for learning: Macro processes and levels of guidance for the roles that implement them
05/08/2008 - 19:31
Facts and data: the foundations for improvement
05/08/2008 - 19:35
The culture's assimilation of change
05/08/2008 - 19:37
The role of the change leader
05/08/2008 - 19:38
The change strategy map
05/08/2008 - 19:39
Aiming at goals
05/08/2008 - 19:41
Measures of effectiveness
05/08/2008 - 19:42
Closing the loop
05/10/2008 - 10:15
Getting control of unnecessary variability
05/10/2008 - 14:29
The execution network
05/15/2008 - 04:01
Spinning the numbers
05/17/2008 - 06:22
Cultural resistance
05/25/2008 - 15:09
Standardizing work and paying piecemeal
05/26/2008 - 12:38
A case study of implementing systematic improvements
05/26/2008 - 13:06
An appeal to politics
05/26/2008 - 13:10
Short attention spans
05/31/2008 - 02:22
The core disciplines - applying the scientific method to process improvement
06/04/2008 - 05:48
The new Geopolitics
06/09/2008 - 06:12
Processes, Mental Models, and Improvement Dynamics
06/17/2008 - 11:46
Diversity
06/20/2008 - 08:26
What in the world is going on?
07/13/2008 - 09:15
Trust, critical thinking, and decision-making
08/23/2008 - 18:53
Faith, hope, and change
09/20/2008 - 09:10
Juggling competing interests
09/28/2008 - 13:07
The turkey before Thanksgiving
09/28/2008 - 13:09
A conflict of visions
09/28/2008 - 13:49
The World is Curved
09/28/2008 - 20:01
When reach exceeds grasp
09/28/2008 - 20:26
Revolution
10/07/2008 - 15:46
The Flaws of the Political System
10/09/2008 - 12:48
What are the systems dynamics of this situation?
10/09/2008 - 12:50
Could this have been anticipated?
10/09/2008 - 12:56
How did the the decision-makers perform?
10/09/2008 - 12:59
What are the critical control points in this system?
10/09/2008 - 13:02
Where does that leave us?
10/09/2008 - 13:04
What should we learn from this?
10/14/2008 - 09:51
Seeing connections that aren't there
10/15/2008 - 11:32
Causation vs Correlation
10/25/2008 - 11:22
Wise decision-making
10/25/2008 - 23:49
How We Think
10/26/2008 - 10:36
Reflecting on a function
10/26/2008 - 10:36
The basis and consequences of mental models
10/26/2008 - 10:44
Reflective thought
10/26/2008 - 10:52
The regulation of thought
10/26/2008 - 11:05
Social influences on beliefs
10/26/2008 - 11:08
Verification of inferences
10/26/2008 - 11:19
The educational transaction
10/26/2008 - 11:24
Thought's natural resources
10/26/2008 - 11:30
Are you going to enforce the rules?
10/26/2008 - 11:35
Mentoring
10/29/2008 - 12:51
Anomalies
10/29/2008 - 12:59
Sharing knowledge
10/29/2008 - 13:02
Exploiting another person's pain
11/02/2008 - 13:17
Timelines
11/10/2008 - 18:13
Pessimism
11/12/2008 - 12:49
Solving problems and selling ideas
11/12/2008 - 12:54
Complexity is slippery
11/15/2008 - 13:00
A user-centered design approach
12/25/2008 - 09:52
Mission critical projects
01/23/2009 - 04:48
Stopping by Woods on a snowy evening
01/23/2009 - 04:52
Wheels between the guardrails
05/04/2009 - 20:23
Using the force
05/29/2009 - 16:56
The dynamics of improvement initiatives
05/30/2009 - 08:48
Translating abstract needs into concrete actions
05/30/2009 - 18:53
Synergy opportunities and risks
05/30/2009 - 19:04
How we decide
06/02/2009 - 09:34
The culture challenge
06/07/2009 - 04:10
Standards and the synergy value proposition
06/10/2009 - 09:10
The troubleshooting path of last resort
06/13/2009 - 14:35
Case study: Providing a utility service to customers
06/19/2009 - 15:44
The map is not the terrain
06/24/2009 - 20:15
Rewired
06/27/2009 - 11:07
Case study: Sharing assets
06/27/2009 - 11:16
Non-linearity
06/29/2009 - 14:50
Beautiful architecture
07/01/2009 - 19:48
Confronting the constraints of synergy initiatives
07/13/2009 - 10:36
Managing business returns on technical software investments
07/15/2009 - 10:32
Are plans worth it?
07/24/2009 - 07:50
Better than bean counting
08/08/2009 - 09:40
An architecture for organizations
08/16/2009 - 12:16
Roles and responsibilities of system development and operational activities
08/17/2009 - 10:24
Development roles and responsibilities for a project team
09/09/2009 - 09:15
Conceptual framework
09/15/2009 - 10:07
Roles and responsibilities of the system operational support team
09/22/2009 - 11:55
Being accountable
10/18/2009 - 10:14
Eschewing Obfuscation
10/19/2009 - 10:39
Shaping the future
10/19/2009 - 16:24
Attention to details
10/22/2009 - 11:28
Self reinforcement
10/25/2009 - 20:31
Rose colored glasses
10/29/2009 - 10:36
Hunches don't work
10/29/2009 - 10:51
Estimates and plans
10/29/2009 - 16:54
Context matters
10/29/2009 - 18:31
Negotiations with senior leaders
11/13/2009 - 22:59
Model distractions
11/27/2009 - 14:38
Delivering sustainable improvements by improving individual and team competency
11/29/2009 - 13:46
Evaluating alternatives
12/01/2009 - 21:59
Vision, strategy, and tactics
12/02/2009 - 09:45
Development is messy
12/15/2009 - 12:25
The basis of estimates
12/15/2009 - 12:26
Securing the commitment
12/17/2009 - 14:06
Sizing up the job
12/17/2009 - 14:08
Resource allocation considerations
12/22/2009 - 10:54
Shaping business targets into realizable commitments
12/22/2009 - 17:18
Are we there yet?
12/29/2009 - 13:42
Profit beyond measure
12/29/2009 - 13:44
Speed of trust
12/31/2009 - 06:34
Bending the curve
01/02/2010 - 17:27
Ski area economics
01/04/2010 - 10:28
Navigating through turbulence
01/05/2010 - 09:38
Software as a service
01/05/2010 - 13:24
Meeting quality expectations
01/07/2010 - 14:12
The promise and perils of the agile movement
01/10/2010 - 05:39
The quest for predictability
01/10/2010 - 12:40
In praise of checklists
01/11/2010 - 12:30
Coordinated teamwork
01/11/2010 - 12:33
Initial medical results
01/11/2010 - 12:35
Root causes
01/11/2010 - 12:37
Grasping the essence of what we know
01/11/2010 - 12:40
Checklists under pressure
01/11/2010 - 12:44
Territoriality
01/11/2010 - 12:47
Professionalism
01/11/2010 - 19:40
Integrated planning is required to satisfy diverse stakeholder needs
01/14/2010 - 12:16
The genesis of checklists
01/14/2010 - 12:26
Managing complexity
01/20/2010 - 15:22
Where does the money go?
01/20/2010 - 21:45
More rowers, fewer coxswain
01/31/2010 - 21:03
Communicating concepts of operations
02/04/2010 - 20:48
Chosing without regret
02/12/2010 - 15:11
Survival depends on it
02/18/2010 - 10:30
Designing effective meetings
02/18/2010 - 14:24
Business cases and return on investments
02/20/2010 - 15:26
Connecting individual and organizational competencies
03/08/2010 - 11:11
Paying for lunch
03/08/2010 - 14:48
How much code is there really in vehicles?
04/01/2010 - 23:34
Confronting uncertainty
04/04/2010 - 14:50
Design's Best Practices might not be
04/09/2010 - 21:11
Discovering your rates of progress
04/15/2010 - 10:07
One event from savagery
04/18/2010 - 14:58
Useful planning by design
04/19/2010 - 11:03
Securing returns from investments
05/25/2010 - 09:52
Dashboard design
05/25/2010 - 10:03
Balanced strategies
05/25/2010 - 10:10
Measures of effectiveness
05/25/2010 - 10:49
Leading indicators
06/07/2010 - 05:04
The elaboration of algorithms
06/07/2010 - 05:15
Problem and solution spaces
06/16/2010 - 15:15
Simplifying complexity
06/17/2010 - 16:30
The motivation
06/17/2010 - 17:04
The opportunity
06/17/2010 - 17:21
The decision-makers
06/17/2010 - 17:35
The mandate
06/17/2010 - 17:53
The criteria
06/17/2010 - 17:57
The evaluation
06/17/2010 - 18:02
The decision and conclusions
06/17/2010 - 20:12
Long-term impacts
06/20/2010 - 14:24
The legacy problem
06/24/2010 - 15:34
Building processes that stand the test of time
06/28/2010 - 10:51
Determining appropriate levels of investment for improvements
07/01/2010 - 12:36
Signal to noise ratio
07/06/2010 - 20:38
How effective are your defect filters?
07/08/2010 - 15:46
Real work
07/08/2010 - 20:59
Becoming competent in managing competency
07/19/2010 - 08:57
Reality
08/18/2010 - 15:14
Looters
08/18/2010 - 21:09
Designing for cohesion
08/20/2010 - 10:55
Designing around constraints
08/28/2010 - 12:25
Honeybees
08/30/2010 - 15:09
Clueless precision
09/02/2010 - 09:27
Our destiny

Drag timeline forward or backward to see more content.