METHODS & SOURCES
The work has a language. This is the working vocabulary behind Tinework’s practice. It defines the method, shows how the terms relate, and names the books, articles, frameworks, and standards that shaped it.
Worked example The method Working ontology Bibliography 01
THE METHOD
One job. One observable workflow. One measured change. Tinework combines four distinct intellectual lineages into a practical sequence for operational work. They are complementary, not interchangeable. The job provides direction. Observation supplies evidence. System redesign changes the work. AI enters only at the task level, where it can be tested.
A
ULWICK / STRATEGYN
Structure the functional job Define the stable job, map its steps, and express success as measurable desired outcomes. This gives the engagement a solution-independent operating frame.
Sources: Anthony W. Ulwick, 2016 , Lance A. Bettencourt and Anthony W. Ulwick, 2008
B
CHRISTENSEN / HALL / DILLON / DUNCAN
Explain progress and circumstance Understand the functional, social, and emotional progress people seek in a particular circumstance—and why they hire one solution rather than another.
Sources: Clayton M. Christensen, 2016 , Clayton M. Christensen, 2016
C
DEMING
Improve the system through learning Treat performance as the product of a system. Make a prediction, test a bounded change, study variation and results, then adjust, adopt, or stop.
Sources: W. Edwards Deming, 1982 / 2018 reissue , W. Edwards Deming Institute, ongoing
D
SVPG / CAGAN & JONES
Empower the team to solve the problem Give a cross-functional team the job, outcomes, evidence, constraints, and business context. Let it discover a solution while testing value, usability, feasibility, and viability.
Sources: Marty Cagan and Chris Jones, 2020 , Marty Cagan, 2018 , Marty Cagan, 2017
01
Define the job Name who needs to accomplish what. Keep the job independent of the software and process used today.
02
Specify the outcomes Translate success into observable directions of improvement. Separate the person’s outcomes from the business measures that justify the work.
03
Observe the work Watch the workflow happen. Capture its steps, decisions, handoffs, systems, exceptions, controls, and evidence.
04
Redesign the workflow Remove work that does not serve the job. Change the sequence and boundaries before adding automation.
05
Allocate the work Assign each step to a person, deterministic software, or AI. Preserve human judgment, escalation, and recovery where they matter.
06
Pilot and learn Test the smallest coherent change against the agreed outcomes. Compare the result with the baseline before wider deployment.
THE METHOD APPLIED TO ITSELF
See the complete consulting workflow. We mapped the Tinework engagement through the same job, workflow, service, state, control, risk, pilot, traceability, and outcome views that an underlying client workflow would receive.
Open the worked example Adopted The term keeps the source method’s essential meaning.
Adapted The source concept is narrowed for workflow consulting.
Tinework synthesis A working definition assembled from several disciplines.
PRODUCT DISCOVERY AND OWNERSHIP
Terms used when a team is responsible for discovering and delivering an operational solution.
Four product risks The value, usability, feasibility, and business-viability questions that a proposed solution must answer.
Adopted Marty Cagan, 2017
03
BIBLIOGRAPHY
Sources and their role in the method. These links point to the author, publisher, journal, or standards body where possible. Inclusion means the source shaped part of the practice. It does not imply endorsement of Tinework’s synthesis.
Tinework does not represent this synthesis as formal ODI, Contextual Design, the SVPG product model, BPMN, or NIST AI RMF compliance. An engagement that uses a source method more strictly will say so in its scope.
01
BOOK
Anthony W. Ulwick. Strategyn, 2016.
HOW IT INFORMS THE PRACTICE
Provides the functional-job, job-executor, job-map, and measurable desired-outcome structure used at the start of an engagement.
Open source ↗ 02
ARTICLE
Lance A. Bettencourt and Anthony W. Ulwick. Harvard Business Review, 2008.
HOW IT INFORMS THE PRACTICE
Shows how to decompose a job from beginning to end without treating the current product or process as the job itself.
Open source ↗ 03
ARTICLE
Clayton M. Christensen, Taddy Hall, Karen Dillon, and David S. Duncan. Harvard Business Review, 2016.
HOW IT INFORMS THE PRACTICE
Adds the progress and circumstance lens that helps explain why someone changes how they accomplish a job.
Open source ↗ 04
BOOK
Clayton M. Christensen, Taddy Hall, Karen Dillon, and David S. Duncan. Harper Business, 2016.
HOW IT INFORMS THE PRACTICE
Formalizes the progress-in-a-circumstance view of a job and the causal question of why people hire, replace, or keep a solution.
Open source ↗ 05
BOOK
Hugh Beyer and Karen Holtzblatt. Morgan Kaufmann / Elsevier, 1997.
HOW IT INFORMS THE PRACTICE
Grounds workflow discovery in observation and interview while people perform real work in context.
Open source ↗ 06
ARTICLE
G. Lynn Shostack. Harvard Business Review, 1984.
HOW IT INFORMS THE PRACTICE
Introduces service blueprinting as a way to make visible actions, supporting work, and failure points inspectable as one system.
Open source ↗ 07
ARTICLE
Michael Hammer. Harvard Business Review, 1990.
HOW IT INFORMS THE PRACTICE
Supports redesigning obsolete work before using technology to make the existing process faster.
Open source ↗ 08
ARTICLE
Lisanne Bainbridge. Automatica, 1983.
HOW IT INFORMS THE PRACTICE
Explains why automation can leave people with harder monitoring and exception work, shaping the method’s human-judgment and control boundaries.
Open source ↗ 09
ARTICLE
Fabrizio Dell’Acqua et al.. Harvard Business School Working Paper 24-013, 2023.
HOW IT INFORMS THE PRACTICE
Provides evidence that generative AI performance varies sharply across tasks, supporting task-level testing instead of broad automation claims.
Open source ↗ 10
FRAMEWORK
W. Edwards Deming Institute. The W. Edwards Deming Institute, ongoing.
HOW IT INFORMS THE PRACTICE
Frames a pilot as a learning cycle with a prediction, an observed result, and an explicit decision to adjust, adopt, or stop.
Open source ↗ 11
BOOK
W. Edwards Deming. The MIT Press, 1982 / 2018 reissue.
HOW IT INFORMS THE PRACTICE
Supplies the system view of management: improve the conditions and process that produce results instead of blaming or optimizing isolated workers.
Open source ↗ 12
BOOK
Marty Cagan and Chris Jones. Silicon Valley Product Group / Wiley, 2020.
HOW IT INFORMS THE PRACTICE
Defines empowered product teams as cross-functional teams given problems and outcomes to own, supported by product vision, strategy, context, and coaching.
Open source ↗ 13
ARTICLE
Marty Cagan. Silicon Valley Product Group, 2018.
HOW IT INFORMS THE PRACTICE
Distinguishes teams trusted to solve important problems from feature teams assigned outputs and prescribed solutions.
Open source ↗ 14
ARTICLE
Marty Cagan. Silicon Valley Product Group, 2017.
HOW IT INFORMS THE PRACTICE
Provides the value, usability, feasibility, and business-viability risk model used to test a proposed solution before scaling it.
Open source ↗ 15
FRAMEWORK
National Institute of Standards and Technology. NIST AI 100-1, 2023.
HOW IT INFORMS THE PRACTICE
Supplies a practical risk-management frame for governing, mapping, measuring, and managing AI throughout its lifecycle.
Open source ↗ 16
STANDARD
Object Management Group. OMG Specification, 2.0.2.
HOW IT INFORMS THE PRACTICE
Supplies a standard vocabulary for representing events, activities, decisions, flows, and participants when a formal process model is useful.
Open source ↗ A LIVING METHOD
Evidence can change the map. The vocabulary will evolve as real engagements expose better distinctions. Changes should preserve the prior definition, explain the reason, and keep the source trail visible.
Share a workflow