An FDE's Week | From Code on Day One to Returning the Learning to the Product on Friday
When we say we can implement faster than anyone, the basis is not fast hands but the fact that the loop of asking, building, reading the reaction, and returning the learning to the product fits inside one week. The seventh article in our FDE practice series lays out that week concretely: Monday's diagnostic and first version, Tuesday to Thursday's observation and daily versions, Friday's KJ session, dictionary update, and pattern-or-branch decision, placing the six skills from the earlier articles into it. It also covers how the weeks stack inside a 45-to-90-day time box until the person on site edits the dictionary and we are no longer needed, how this differs from contract-development phases, and, honestly, what does not reach production in a week.
