KSD study plan

Map each of the six KSD domains to its weight and write a one-line definition of service, purpose, and demand in your own words

Distinguish the customer, the service, and the system of work for two real services you know from experience

List the four classes of service (expedited, fixed date, standard, intangible) and assign three example work items to each

Draft a one-page purpose statement for a service you actually support, naming who it serves and what outcome it produces

Write a policy for each class of service stating target lead time, acceptable risk, and who may expedite

Identify two capacity constraints in your service and estimate their throughput in items per week

Compare push scheduling with pull-based commitment and explain when each is appropriate

Define what 'done' means at each handoff stage in a workflow you know

Build a simple board with columns that match real handoffs, not org chart roles

Set explicit WIP limits per column and justify each number against capacity

Model a pull signal: state what event authorizes the next item to start

Trace one item end to end and mark where it waited versus where it was worked on

Collect one week of flow data: arrival dates, start dates, finish dates, and wait time per stage

Calculate lead time, touch time, and flow efficiency for at least ten completed items

Plot a cumulative flow diagram from the collected data and describe where the band widens

Identify the single largest queue and state its cost in delay terms

Run one retrospective structured around flow signals rather than opinions

Convert one observed problem into a falsifiable experiment with a predicted outcome and a review date

Identify a reinforcing loop and a balancing loop in your system and draw both

Name two local optimizations that would harm overall flow and explain why

Draw a system map showing demand sources, value streams, and feedback paths for your service

List the dependencies between teams that most delay delivery and rank them by delay caused

Prepare STATIK inputs: identify the service, its customers, and the sources of demand

Run the STATIK sequence on paper from purpose through to classes of service and policies

Derive a candidate set of services from STATIK output and test each against the purpose statement

Write discovery questions you would ask stakeholders to validate demand assumptions

Select two candidate services to model further and justify the choice

Identify what evidence would cause you to split or merge a service

Review the week-5 experiment result and decide whether to adopt, adapt, or abandon it

Recompute flow efficiency and lead time and compare against week-4 baseline

Write the next experiment with a clearer metric and a shorter cycle

Assemble a one-page summary of the whole system and the current constraint