Redo

Users work differently from makers, for good reason. If you make a mistake buying a book on Amazon, you can usually go back an action, or a screen, call it a redo. Makes sense to just keep hammering keys until you get what you want.

Makers often don’t have redo, so there’s an emphasis on using a planning and structure to reduce rework. I cut that board three times and it’s still too short! Well then, Measure twice, cut once.

Working in an IDE (Integrated Development Environment – programmer’s code-making software) discovering an error can require taking out days of development.

The old observation that one programmer can do the work of a thousand programmers is valid because many programmers spend the next morning tearing up whey did the previous day. One step forward, two steps back.

Sales Lab’s Planned Workcycle addresses the need for Architecture and Design before Executing, and came from construction contracting. If you order a crane, it better be busy the whole time it is on-site, and after it leaves, you best not need that crane again.

The Workcycle also has an original structure for how to do Evaluation which makes Evaluation work a whole lot better. I’ve found it increases efficiency in many types of complex projects.

How does the availability of Redo change the value of Planning, the process of Executing?