"Happy People do Good Work" and "Good Work makes People Happy"
I use my experience to discover how to optimize Workflows helping teams help People
For 30 years, I've been helping technical teams build better processes by focusing on people, collaboration, and meaningful improvements.

The human approach to technical Workflow Analysis
See Jostle for Co-Creation and working together

Build trust that the system the team creates together will be designed to catch each other!

Build Agile and live a culture that works in time, and not against it.
Kanban did not start in a software company. It started with a loom that could stop itself in 1896 — and a factory culture that trusted people to stop the line.
Read the history →You don't install Agile. You grow it. A practical path: write down how you work today, then iterate with weekly Kanban meetings and sprints that deliver value.
See how a place becomes Agile →Two weeks is the perfect sprint cycle — mainly for human habits. Just over two dozen sprints a year, each one a considered deliverable of value.
Why two weeks wins →Years of building software teams have convinced me that four perceptions of work contribute most to a person's success and happiness:
Autonomy · Mastery · Liking the people you work with · Knowing what you do is important
Using Charlie Munger's inversion technique — ask "What makes us miserable at work?" — and then design the workflow so people can be valuable without friction. That is Flow: the state where challenge and skill balance, and good work feels effortless.