Post #4272596
2026-07-31 08:57 UTC
@nobsagile@mastodon.social @scrumschau@mastodon.social It's a similar model, absolutely. The main difference is that I measure feedback latency in consequent decisions instead of time. I've been playing with visualising design processes as trees, like this one.
Replies (2)
-
@jasongorman@mstdn.business 2026-07-31 08:58
@nobsagile@mastodon.social @scrumschau@mastodon.social Some interesting analogs have fallen out of it around, for example, optionality
-
@JeffGrigg@mastodon.social 2026-07-31 15:09
@jasongorman@mstdn.business @nobsagile@mastodon.social @scrumschau@mastodon.social Most interesting diagram. Insightful. But I have to wonder ... If "Decision One" (D1) was wrong/invalidated, does that not call *everything in the entire tree* into question? *ALL other decisions* seem to depend on it. Maybe if D3 and D4 were wrong, we'd only lose 60% of the work -- > (Perhaps an "invalidation" of a decision may be partial -- so only a partial loss to its children.)