Week by Week: The Complete CCF Deployment Calendar for Atelier Owners Who Are Done Theorising
The previous four articles in this series built the case. They established the science of why bundled systems outperform isolated interventions, stress-tested the CCF’s three pillars against every serious methodological objection in the peer-reviewed literature, specified the five prerequisite conditions that must be present before implementation begins, and introduced three novel theoretical constructs for the doctoral community. If you have read all four, you know more about the management science of craft enterprise transformation than most consultants who will ever walk through your studio door.
You are also, if you are honest with yourself, still sitting with the same question you had at the end of the first post. Not whether it works. Whether you can actually do it — in a studio with thirteen people, three benches, a December season eight weeks away, and a founder who still catches himself adjusting work that has been signed off by the responsible artisan.
This article answers that question. Not with more theory. With a week-by-week protocol.
The 90-Day Protocol is a structured organisational intervention with specific weekly actions, measurable milestones, and documented failure modes at each stage. It is designed to be completed without external facilitation — although facilitation accelerates it. It requires approximately four hours of founder time per week above normal operations across the first ten weeks, reducing to approximately two hours per week in weeks eleven through thirteen. It will produce a measurable productivity decline in weeks five through nine. This decline must be anticipated, documented, and not misread as evidence that the system is failing — because misreading it is the single most common reason CCF implementations collapse before they produce results.
Before reading further, complete one prerequisite step if you have not already done so: score yourself against the 25-question Studio Readiness Diagnostic in the previous article. A score below 40 means the prerequisite development work should precede this protocol by three to six months. A score between 40 and 59 means you can begin the protocol now, but specific prerequisite gaps require parallel attention. A score of 60 or above means you are ready to begin Week 1 this coming Monday.
The Architecture of the 90 Days
The protocol operates in three phases, and the sequence is non-negotiable. Milgrom and Roberts (1995) established that partial adoption of a complementary system — introducing one component without the others — produces a performance valley in which the costs of transition are incurred without the synergistic returns that only materialise at full system integration. The sequencing rule is more specific than this: the motivational substrate must be prepared before the structural routines are introduced, and the structural routines must be operational before the verification layer is deployed. Reversing this sequence does not merely slow the system down — it produces the failure modes described in the fifth section of this article.
Phase 1, covering Weeks 1 through 3, is the Foundation Phase. No pillar is deployed here. This phase is entirely concerned with the two prerequisites that the previous article identified as most critical: psychological safety and the founder identity transition. Adler and Borys (1996) established that enabling formalisation — the kind of routine structure that converts motivated artisans into consistently excellent performers — requires a motivational foundation. You cannot build the enabling architecture before the motivational climate exists to receive it.
Phase 2, covering Weeks 4 through 10, is the Pillar Activation Phase. The three pillars are introduced in AMO sequence: Motivation first (Pillar 1 — Psychological Empowerment, Weeks 4–5), then Opportunity (Pillar 2 — Habit-Based Routines, Weeks 7–8), then Ability verification and meaning amplification (Pillar 3 — Digital Passport, Weeks 9–10). Week 6 is the implementation dip week — the point at which the new system’s costs are highest and its returns are not yet visible. It has its own entry in this protocol.
Phase 3, covering Weeks 11 through 13, is the Integration and Measurement Phase. The full system is operational. The first measurement comparison is conducted against the Week 4 baseline. The 90-day review is held with the full team. Lally, van Jaarsveld, Potts, and Wardle (2010) established that habit formation takes between 18 and 254 days, with a mean of 66 days. At Day 90, the CCF’s habit routines are in their early stabilisation phase — working but not yet automatic. The protocol produces a working system, not a completed one. The completion comes from the 12 months that follow.
Phase 1 — Foundation: Weeks 1 to 3
Week 1 — The Founder Assessment. This week belongs entirely to you. Nothing is communicated to the team. Nothing changes on the bench. The work of Week 1 is internal, honest, and uncomfortable in proportion to how much of it applies to you.
Complete the 25-question Studio Readiness Diagnostic if you have not already done so. Then complete the five-question Psychological Safety Diagnostic. Then read the seven behavioural signatures of defensive identity work and count how many you recognised in your own conduct in the last thirty days. Write your count down. Do not moderate it upward for comfort or downward for humility. The number is the baseline.
The Week 1 deliverable is a single document: a written founder commitment statement containing three specific behavioural commitments for the next twelve weeks. Not aspirations. Specific, observable behaviours that another person could verify. Examples of inadequate commitments: “I will delegate more” — too vague. “I will trust my team” — not measurable. Examples of adequate commitments: “I will not physically adjust work on the bench that has been signed off by the responsible artisan without first having a conversation with them about the specific concern.” “I will conduct the end-of-day bench review at least four times per week for the first eight weeks.” “When I make a technical error on the bench this week, I will name it out loud in front of whoever is working nearby.”
Write the three commitments. Sign and date the document. Place it where you will see it at the start of each working day for the next twelve weeks.
Milestone Week 1: Founder has a documented baseline score and a signed three-commitment statement.
Week 2 — The Safety Pre-Flight Begins. Edmondson (1999) established that psychological safety is a team-level climate produced through repeated, visible demonstrations that interpersonal risk-taking is safe. It is not produced through policy announcements or management declarations. It is produced through behaviour — specifically, through the leader’s demonstrated willingness to be wrong in public.
This week, introduce the Active Error Modelling protocol. The format is simple: in at least two bench interactions this week, you name a technical decision you made that produced a suboptimal outcome. Not a disaster. Not an exception to your usual standard. An ordinary, recoverable imperfection of the kind that every jeweller produces and almost no founder names out loud in front of their team.
The framing matters. “I mis-estimated the bezel height on the Hendricks commission and had to rework the setting. Here is what I would do differently next time” is an Active Error Model. “I almost made a mistake today but caught it in time” is not — it reinforces infallibility rather than dismantling it. Nembhard and Edmondson (2006) found that leader inclusiveness — the explicit invitation for lower-status team members to contribute — is the primary moderator of psychological safety in status-differential teams. Active Error Modelling is the most direct form of inclusiveness available: it demonstrates that the standard applies to the master as well as the apprentice.
Also this week, introduce the end-of-day bench review. Ten minutes. Standing. At the end of the production day. The question is always the same: “What did you notice today?” The founder’s role in this conversation is to listen and ask one follow-up question per response. No evaluation. No correction. No “yes, but.” Just attention and curiosity. Document each review in a simple log: date, who was present, what was said.
Active Error Modelling Log — Week 2 Format:
| Date | Situation | Error Named | Learning Framed |
|---|---|---|---|
| __/__ | Describe the context in one sentence | What specifically went wrong or suboptimally | What you would do differently next time |
| __/__ |
Milestone Week 2: Two Active Error Modelling instances documented in the log. End-of-day bench review conducted at least three times.
Week 3 — The Identity Bridge First Experiment. Select the first delegation experiment. The criteria for selection are specific: the commission must be within the designated artisan’s demonstrated technical competence, the client relationship must have sufficient trust to absorb a minor quality variation from your personal standard, and the piece must have sufficient margin in the schedule that a midpoint review conversation does not create production pressure. If no current commission meets all three criteria, wait until one does. Do not force the experiment onto an unsuitable commission.
Brief the artisan fully — materials, client brief, quality standard, timeline. Then step away from the piece. Do not return to it until the scheduled midpoint review at the midpoint of the production timeline.
The midpoint review uses a structured format. Three questions only, in this order. First: “What has gone well so far?” Listen fully before responding. Second: “What has been challenging?” Listen fully. Do not immediately offer solutions. Third: “What do you need to complete the piece to the standard we agreed?” This third question is the delegation experiment’s critical moment — it offers support without substituting your judgment for theirs. If they ask for your technical input directly, provide it. If they do not ask, do not offer it.
Ibarra (1999) established that identity transitions require low-stakes experiments before high-stakes commitments. This commission is your first provisional self experiment as the Architectural Founder — the person who builds the system within which the next generation of craftspeople can approach mastery. It will feel uncomfortable. That discomfort is the experiment working.
Milestone Week 3: Delegation experiment initiated, midpoint review conducted, founder has not physically touched the piece between briefing and midpoint review.
Phase 2 — Pillar Activation: Weeks 4 to 10
Week 4 — Pillar 1 Launch: Baseline Measurement. Administer the 12-item dual-level empowerment measurement instrument from the previous article anonymously to the full team. Anonymous administration is non-negotiable: team members will not report honest scores if they believe the results are individually attributable. Use paper forms collected in a single envelope, or a digital survey with no identifying fields.
Score the results and prepare a heat map of the distribution — not averages, distributions. The heat map should show the spread of scores across the four individual empowerment dimensions and four team empowerment dimensions, without individual attribution. The variance detection items should be scored separately and reported separately: these are the questions that surface hidden pockets of disempowerment that the averages conceal.
Hold a 45-minute team meeting to share the results. Your opening statement sets the entire tone for what follows: “I asked you these questions because I want to understand what this studio feels like to work in, not just what it looks like from where I stand. Here is what the scores show. I am going to share all of it — including the parts that are uncomfortable — because you deserve to know what you told me.” Show the distribution. Name the dimensions where scores are lowest. Ask one question and then listen: “Looking at these scores as a team, what would need to be true in this studio for everyone to score one point higher on the meaning dimension?” Document every response. These responses are the design brief for Pillar 1.
Week 4 Empowerment Heat Map Format:
| Dimension | Scores 1–2 (count) | Scores 3 (count) | Scores 4–5 (count) | Flag |
|---|---|---|---|---|
| Meaning (individual) | Red if >30% score 1–2 | |||
| Competence (individual) | ||||
| Self-determination | ||||
| Impact (individual) | ||||
| Team potency | ||||
| Team meaningfulness | ||||
| Team autonomy | ||||
| Team impact | ||||
| Variance — inclusion | Red if any item <2.0 avg | |||
| Variance — voice safety | ||||
| Variance — equal trust | ||||
| Variance — input sought |
Milestone Week 4: Baseline measurement complete, heat map distributed to team, team input collected and documented.
Week 5 — Pillar 1 Design and Communication. Review the team input from Week 4. Identify the three specific changes that would most directly address the lowest-scoring empowerment dimensions. Each change must be concrete enough that the team can verify whether it happened. Each must address one of Spreitzer’s (1995) four dimensions: meaning (is the work experienced as purposeful?), competence (are artisans trusted with decisions that match their capability?), self-determination (do artisans have genuine discretion over method?), or impact (do artisans see how their work affects outcomes?).
Communicate the three changes to the team with explicit reference to the Week 4 data. The structure of the communication is precise: “You told us [specific finding from measurement]. So we are changing [specific action]. This change takes effect from [specific date].” This transparency is the enabling formalisation moment Adler and Borys (1996) describe: the team can trace the connection between their honest input and the system’s response. This traceability is what converts a management announcement into an empowerment signal.
Milestone Week 5: Three empowerment changes documented in writing, communicated to team with explicit data reference, implementation dates confirmed.
Week 6 — The Implementation Dip. This week will feel like the system is failing. It is not. It is doing exactly what Repenning and Sterman (2002) described: incurring the transition costs that precede the performance gains. The new work assignment protocols from Week 5 are unfamiliar. The bench reviews are still effortful. The delegation experiment has produced at least one outcome the founder would have done differently. Production throughput will likely decline by 10 to 15% against the prior four-week average.
Your task this week is not to fix the dip. It is to document it precisely enough to distinguish it from a structural failure. The following tracking table is your diagnostic instrument.
Week 6 Implementation Dip Tracking Table:
| Metric | 4-Week Prior Average | Week 6 Actual | Status | Trajectory |
|---|---|---|---|---|
| Jobs completed per week | D / S / I | ↓ toward floor / ↓ still falling | ||
| Founder bench interventions | D / S / I | |||
| Team-initiated decisions | D / S / I | |||
| End-of-day review participation | D / S / I | |||
| Active Error Models this week | D / S / I |
Status codes: D = Declining, S = Stable, I = Improving. The dip diagnosis: if jobs completed is declining but stabilising (trajectory: approaching floor), founder bench interventions are stable or declining, and team-initiated decisions are stable or improving — this is the implementation dip. Continue the protocol. If jobs completed is still falling with no floor in sight and team-initiated decisions are also falling — this is a structural problem requiring diagnosis. Pause and identify which prerequisite is absent.
Milestone Week 6: Dip tracking table completed, dip vs. structural failure diagnosis documented, protocol continuation confirmed or pause decision made with written reason.
Week 7 — Pillar 2 Introduction: The First Habit Routine. Do not introduce multiple routines this week. One. Wood and Neal (2007) established that habit formation requires context-triggered automaticity — a consistent cue that reliably initiates the routine behaviour. Multiple simultaneous routines compete for the limited attentional resources available during the new behaviour’s pre-automatic phase. Lally et al. (2010) confirmed that parallel habit formation extends formation time for all habits involved. One routine. Fully embedded. Then the next.
Select the routine by identifying the single highest-friction operational handoff in the studio — the transition point where work most often stalls, is returned for clarification, or requires re-briefing. Common candidates in jewellery studios: the briefing-to-bench handoff (the point where client specifications reach the responsible artisan), the bench-to-setting handoff (the point where the fabricated piece reaches the setter), or the final inspection handoff (the point where completed work reaches quality review before client delivery).
Design the routine using the following template. Five steps maximum. Each step must be completable in under two minutes. The final step must include a definition of “complete” — the specific condition that tells the next person in the chain that the handoff is ready to receive.
Habit Routine Design Template:
- Cue: [Specific trigger that initiates the routine — e.g., “When the fabricated piece is ready for setting”]
- Step 1: [First action — e.g., “Complete the job card with current stage, any material notes, and estimated completion time”]
- Step 2: [Second action]
- Step 3: [Third action]
- Completion definition: [Specific, observable condition — e.g., “Job card is complete, piece is in the designated handoff tray, setter has acknowledged receipt”]
Introduce the routine at the next team meeting with the Adler and Borys (1996) enabling framing: “This routine exists to reduce the friction at this specific handoff point. It does not tell you how to do your work. It tells you what ‘ready to hand off’ looks like so that the next person can begin without chasing information. It is a tool for you, not a supervision mechanism for me.” This framing determines whether the routine is experienced as enabling or coercive — and that experience determines whether it produces the empowerment amplification effect or the motivation crowding effect.
Milestone Week 7: One habit routine designed using the template, introduced with enabling framing, first execution documented.
Week 8 — Pillar 2 Consolidation. The Week 7 routine is in its second week. Feldman and Pentland (2003) distinguished between the ostensive aspect of a routine — what it is designed to do — and the performative aspect — what it actually does in practice. In the first two weeks of a new routine, the performative aspect diverges from the ostensive in ways that are predictable and addressable. Some team members will find shortcuts. Some will add steps the template did not include. Some will execute the routine fully and find it genuinely useful. All of these responses are data.
This week, conduct a ten-minute review of the routine with the team. Ask three questions: what about this routine is creating less friction than before, what about it is still frustrating or awkward, and what one change would make it work better? Make one adjustment based on the team’s feedback. Document the original design and the adjustment. This is not a failure of the original design — it is the co-design process that converts an imposed procedure into an owned tool. A routine that the team has adjusted is a routine the team owns.
Milestone Week 8: Routine review conducted, one adjustment documented, original and revised versions both recorded.
Week 9 — Pillar 3 Introduction: The Meaning Conversation. Before the first Digital Passport record is created, a conversation must happen. Not a technical briefing. Not a system demonstration. A conversation about what the record means.
Jiang and Cheng (2025) established that digital verification systems increase work engagement specifically when they activate the meaning dimension of psychological empowerment — when the record is experienced as validation of craft expertise rather than monitoring of output. Frey and Jegen (2001) established the cost of getting this wrong: external verification perceived as control crowds out the intrinsic motivation it is designed to support, producing passive compliance rather than the craft identity investment the system requires. The Week 9 conversation is the design condition that determines which of these outcomes the Digital Passport produces in your studio.
Hold a 30-minute team conversation using the following guide. Read the four framing statements before asking the questions. Allow silence after each question. Do not fill it.
Transparency Equity Conversation Guide:
Framing statement 1: “This record belongs to you. Not to me, not to the studio, not to the client. To you.” Framing statement 2: “When you leave this studio — whether in two years or in twenty — you take your record with you. It is your professional portfolio. It is proof of what you made, at what standard, under what conditions.” Framing statement 3: “I will have access to your record. So will you. I will not use your record to evaluate your performance without having a direct conversation with you first. Your record is not a performance review tool.” Framing statement 4: “If at any point you feel this record is being used in a way that was not agreed today, I want you to tell me directly. That is not disloyalty. That is the system working as it should.”
Then ask three questions. Question 1: “What would make you feel genuinely proud to have your name on a record like this?” Question 2: “What would make you uncomfortable about having your work documented in this way?” Question 3: “What would I need to do — or not do — for this record to feel like yours?”
Document all responses. The answers to Question 2 are your implementation risk register for Pillar 3. Address each concern explicitly before the first record is created.
Milestone Week 9: Meaning conversation conducted, all four framing statements delivered, team responses to all three questions documented, explicit artisan consent obtained for record creation.
Week 10 — Pillar 3 First Records. Create the first Digital Passport records for the three highest-value pieces currently in production. The process is non-negotiable on one point: the responsible artisan enters their own information, reviews the record before submission, and receives a copy. The founder does not create the records unilaterally. The artisan’s hands are on the keyboard. This is not inefficiency — it is the ownership transfer that makes the Transparency Equity commitment operational rather than rhetorical.
Document the time required per record. If it exceeds fifteen minutes, the workflow requires optimisation before full deployment. The three-layer Hybrid Architecture — Layer 1 off-chain legal document, Layer 2 Polygon timestamp, Layer 3 IPFS media — should be operational by this week. If the technical infrastructure is not yet in place, Week 10 creates the Layer 1 documents only and notes the Layer 2 and Layer 3 submission as pending. A complete record created in stages is preferable to a delayed record waiting for full infrastructure.
Verify the physical-digital binding for each piece: the laser-inscribed girdle identification number recorded in the Layer 1 document, the stone examined under 10× magnification to confirm the inscription matches the record. If any piece does not have a girdle inscription, note this limitation explicitly in the record. A provenance record that discloses its limitations is more credible than one that implies completeness it cannot deliver — Spence (1973) on costly signalling applies to the record’s honesty as much as to its existence.
Milestone Week 10: Three passport records created with artisan involvement, time-per-record documented, physical-digital binding verified for each piece.
Phase 3 — Integration and Measurement: Weeks 11 to 13
Week 11 — Full System Operation. All three pillars are now active. The empowerment changes from Week 5 are in their seventh week. The first habit routine is in its fifth week — approaching the early automaticity threshold Lally et al. (2010) identify for simple procedural habits. The Digital Passport is in its second week of operation.
This week, introduce the second habit routine. Use the same selection criteria as Week 7: the second-highest-friction operational handoff in the studio. Use the same design template. Use the same enabling framing at the team introduction. The introduction of the second routine in Week 11 — rather than Week 7 — is deliberate. The first routine needs four weeks of consolidation before a second competes for attentional resources. This sequence is the CCF’s operational translation of Lally et al.’s (2010) finding on parallel habit formation interference.
Milestone Week 11: Second habit routine introduced with enabling framing, full three-pillar system confirmed operational, second routine first execution documented.
Week 12 — Fidelity Assessment. Re-administer the 12-item dual-level empowerment instrument to the full team using the same anonymous administration protocol as Week 4. Score the results using the same heat map format. Prepare the delta table comparing Week 4 and Week 12 scores dimension by dimension.
Week 12 Fidelity Assessment Delta Table:
| Dimension | Week 4 Average | Week 12 Average | Delta | Direction | Flag |
|---|---|---|---|---|---|
| Meaning (individual) | ↑ / → / ↓ | ||||
| Competence (individual) | |||||
| Self-determination | |||||
| Impact (individual) | |||||
| Team potency | Expect lag vs. individual | ||||
| Team meaningfulness | |||||
| Team autonomy | |||||
| Team impact | |||||
| Variance — inclusion | Red if still <2.0 | ||||
| Variance — voice safety |
Expected pattern at Week 12: individual meaning and self-determination scores should show improvement above Week 4 baseline. Team potency scores typically lag individual scores by two to four weeks — this is normal and does not indicate system failure. Chen, Kirkman, Kanfer, Allen, and Rosen (2007) established that team-level empowerment constructs develop more slowly than individual-level ones because they require collective sensemaking, not just individual psychological shifts.
If any subgroup — apprentices, junior polishers, or any role cohort — shows no improvement or declining scores while the full-team average has improved, this is the aggregation problem made visible. The average is masking a structural pocket of disempowerment that requires targeted intervention before the system can produce its supermodular returns. Identify which subgroup and investigate the specific cause before proceeding to the 90-day review.
Also this week, conduct a personal reassessment against the seven behavioural signatures of defensive identity work. Count how many you recognise in your conduct over the past four weeks. Compare to your Week 1 count. The reduction in this number — not the absolute score — is the identity transition metric. Petriglieri (2011) established that identity threat is managed through progressive identity expansion rather than through single transformative events. A reduction of two or three behaviours over twelve weeks is a meaningful identity transition. A reduction of zero indicates the identity work requires additional attention before full delegation is possible.
Milestone Week 12: Week 12 measurement complete, delta table prepared, subgroup variance analysed, founder behavioural signature reassessment documented.
Week 13 — The 90-Day Review. Sixty minutes. Full team. No agenda distributed in advance. The founder’s opening statement: “Thirteen weeks ago we began something. I want to know honestly what you think about where we are.”
The review uses four structured questions, asked in sequence with sufficient time between each for genuine responses. Document every substantive comment.
90-Day Review Protocol — Four Questions:
- “What is working better in this studio than it was thirteen weeks ago?” — Allow three to five minutes for responses. Do not qualify or contextualise what you hear. Record it.
- “What is not yet working as it should?” — This question will produce silence before it produces honesty. The silence is the Safety Pre-Flight working. Hold it for at least thirty seconds before prompting. Record everything, including the tone of the responses.
- “What one change would make the biggest difference to how this studio operates in the next thirteen weeks?” — One change per person. No commentary from the founder during this question. Just recording.
- “What do you need from me that you are not currently receiving?” — This is the hardest question for a founder to ask and the most valuable one to hear answered honestly. The Safety Pre-Flight’s effectiveness is visible in the quality of the responses to this question. If responses are polite and non-specific, the psychological safety work is not complete. If responses are specific and direct — even uncomfortable — the climate is working.
After the review: within 48 hours, send the team a written summary of what you heard and three specific commitments you are making in response to Question 4. This closes the loop that the Week 5 data-to-action communication opened. The team told you something. The system responded. The founder is accountable to what they heard.
Milestone Week 13: 90-day review conducted, all four questions asked and documented, written response with three specific commitments delivered to team within 48 hours.
The Failure Mode Map
Seven failure modes account for the majority of CCF implementation collapses. Each is described below with its behavioural signature, its typical timing, its cause, and its recovery protocol. The recovery protocols are designed to be followed without external facilitation. If you are in a failure mode and the recovery protocol does not produce visible change within two weeks, external facilitation is recommended.
Failure Mode 1 — The Pre-Flight Skip. The founder begins Week 4 Pillar 1 activities without completing the Week 2 and Week 3 Safety Pre-Flight protocols. Signature: team engages politely with empowerment conversations but produces no change in independent decision-making rates over six weeks. Timing: visible by Week 8. Cause: psychological safety is insufficient for genuine interpersonal risk-taking — artisans are performing engagement rather than experiencing it. Recovery: pause all Pillar 1 activities. Return to Week 2. Complete four full weeks of Active Error Modelling and end-of-day bench review before re-attempting the Week 4 baseline measurement. Do not abbreviate the Safety Pre-Flight a second time.
Failure Mode 2 — The Identity Relapse. The founder completes the Week 3 delegation experiment but reverts to bench adjustment and approval-seeking under production pressure — typically in the pre-December peak or when a high-value commission is in progress. Signature: delegation experiments are technically completed but the founder has physically touched the piece between briefing and delivery without the artisan’s direct request. Timing: Weeks 6–8 under production pressure. Cause: identity threat triggered by visible quality variance from the founder’s personal standard. Recovery: Ibarra’s (1999) provisional selves protocol — reduce the scope of the next delegation experiment to a component task rather than a complete commission. Rebuild identity confidence at lower stakes before returning to full commission delegation. Document the reduction explicitly: “I am deliberately choosing a smaller delegation scope this week to practice the non-intervention behaviour, not because the artisan is not capable.”
Failure Mode 3 — The Dip Misread. The founder interprets the Week 6 productivity decline as evidence that the system is failing and scales back or abandons the protocol. Signature: routine removed, empowerment conversations suspended, return to prior operating mode. Timing: Week 6, almost exclusively. Cause: Repenning and Sterman (2002) capability trap — the normal costs of transition are misattributed to structural system failure. Recovery: if the system has been partially abandoned, a full restart from Phase 1 is required. Partial restarts do not produce the complementarity effects — they produce the Milgrom and Roberts (1995) partial adoption valley at a lower altitude than the original attempt. Before restarting, complete the following diagnosis: was the Week 6 decline accompanied by a floor (metrics declining toward stabilisation) or was it a freefall with no floor? If it had a floor, it was the dip. Restart from Week 1 with this knowledge explicit.
Failure Mode 4 — The Coercive Drift. The Digital Passport is introduced without the Week 9 meaning conversation, or the founder begins using passport data to monitor artisan output rather than to document artisan achievement. Signature: artisans entering minimum required data, no voluntary engagement with records, Digital Passport records are accurate but thin. Timing: visible within two weeks of first record creation. Cause: Frey and Jegen (2001) motivation crowding — the extrinsic control signal has displaced intrinsic motivation to document. Recovery: suspend Digital Passport use for one week. Conduct the Transparency Equity conversation retroactively — include the honest acknowledgment that the system may have felt like surveillance and that this was not the intent. Implement the governance change explicitly: transfer record ownership to the artisan — they receive a copy of every record they create, they can access their full record at any time without requesting it from the founder, and their record is not referenced in any performance management conversation without advance notice.
Failure Mode 5 — The Routine Overload. Multiple routines are introduced simultaneously in Week 7 rather than sequentially. Signature: team compliance declines across all routines simultaneously, artisans report feeling overwhelmed, production quality dips sharply and does not stabilise within two weeks. Timing: Week 8, following simultaneous Week 7 introduction. Cause: cognitive overload — parallel habit formation competes for attentional resources in a way that sequential formation does not. Recovery: immediately reduce to one active routine — the one the team reports as most useful. Allow six weeks of stabilisation before introducing the second. Document the lesson: the protocol specifies one routine per introduction point for this reason.
Failure Mode 6 — The Measurement Bypass. The Week 4 empowerment measurement is skipped or replaced with the founder’s subjective impression of team morale. Signature: founder reports the team is “doing well” or “seems more engaged” but cannot quantify the change or identify which dimensions have improved. Timing: detectable at Week 12 when no baseline exists for delta comparison. Cause: measurement anxiety, time pressure, or the belief that qualitative observation is sufficient. Recovery: administer the 12-item instrument immediately. Acknowledge to the team that the Week 4 baseline was not collected and that the Week 12 scores are therefore the first data point rather than a comparison. Kirkman and Rosen (1999) on team empowerment and Seibert et al. (2011) on the empowerment-performance correlation are explicit: without measurement, the CCF has no feedback mechanism. The system operates blind.
Failure Mode 7 — The Partial System Trap. Two pillars are deployed and the third is indefinitely delayed. Signature: studio reports modest performance improvement but reaches a plateau without further gain; founder reports the system is “working well enough” to not require the third pillar. Timing: Weeks 12–16, following successful two-pillar deployment. Cause: Milgrom and Roberts (1995) partial adoption valley — two-pillar performance is better than the prior state but substantially below the supermodular returns that only the three-pillar system produces. The improvement from two pillars is real; it creates a comfort trap that prevents the additional investment required for the third. Recovery: diagnose which pillar is absent. If Pillar 3 is missing, the barrier is usually the Week 9 meaning conversation — the founder’s reluctance to make the Transparency Equity commitment. If Pillar 1 is partial (present in form but not in substance), the barrier is usually the identity transition — the founder who has introduced empowerment language but has not changed the bench behaviours that signal actual authority. Name the barrier directly and address it specifically.
The Post-90-Day Architecture
At Day 90 the CCF is a working system, not a completed one. The distinction matters for what comes next. A working system requires maintenance, calibration, and periodic honest assessment of whether it is still functioning as designed. A completed system requires only monitoring. The CCF is never completed — it is continuously developed, because the studio it governs is continuously developing.
The post-90-day maintenance architecture operates on four cadences. Quarterly — every thirteen weeks — the dual-level empowerment instrument is re-administered to the full team. Results are reported to the team as distributions, not averages. Variance detection items are analysed for emerging pockets of disempowerment before they become structural problems. The delta from the previous quarter’s baseline is the primary metric: the direction of change matters more than the absolute score.
Annually, every twelve months, the following four reviews are conducted. The routine audit: each active habit routine is reviewed for Feldman and Pentland (2003) ostensive-performative alignment. Has the routine’s actual execution in practice drifted from its designed purpose? Are team members following the letter of the routine while working around its intent? The audit question for each routine is: does this routine currently reduce friction, or has it become a compliance exercise that the team executes to satisfy a requirement rather than to improve their work? Routines that have drifted require redesign, not removal.
The succession readiness assessment: once per year, the founder assesses the studio’s operational independence using the succession economics framework from the previous article. The specific metric is the EBITDA multiple equivalent — what would a sophisticated buyer pay for this studio today, and how does that compare to twelve months ago? The target trajectory is 0.3 to 0.5 multiple points of improvement per year over a three-year horizon, from a starting point of 3 to 4 times to a target of 5.5 to 7 times at the end of the CCF’s primary implementation cycle.
The Digital Passport governance review: audit the Hybrid Architecture for Protection of Personal Information Act compliance, test the physical-digital binding on a sample of ten pieces by verifying girdle inscriptions against Layer 1 records, confirm Layer 2 Polygon transaction accessibility for all records created in the past twelve months, and verify Layer 1 off-chain document security and backup integrity. Walch (2019) on blockchain governance risks and De Filippi and Wright (2018) on lex cryptographia establish the standard: the legal record must be independently accessible regardless of the blockchain network’s current state. The annual governance review verifies this independence.
The NQF alignment review: for studios participating in the MQA discretionary grant programme or pursuing NQF Level 5 supervisory qualification for artisan staff, the post-90-day system provides the work-integrated learning evidence base required for formal assessment. The habit routine documentation records constitute structured workplace learning evidence. The Digital Passport service records constitute competency demonstration artefacts. The empowerment measurement data constitutes workplace development tracking. The 90-day protocol, deployed with appropriate assessment instrument alignment, produces the portfolio evidence that workplace-based qualification requires — without creating additional documentation burden beyond the system the studio is already maintaining.
12-Month Milestone Framework:
| Milestone | Month 3 | Month 6 | Month 12 |
|---|---|---|---|
| Individual empowerment avg | +0.3 above baseline | +0.5 above baseline | +0.8 above baseline |
| Team potency avg | Stable or improving | +0.3 above baseline | +0.6 above baseline |
| Founder bench interventions | -20% vs. Week 1 | -35% vs. Week 1 | -50% vs. Week 1 |
| Active habit routines | 2 fully operational | 3 operational | 4 operational, 1 under review |
| Digital Passport records | All pieces >R15k | All pieces >R8k | All commissioned pieces |
| Succession multiple equiv. | Baseline established | +0.2 above baseline | +0.4 above baseline |
| Variance detection (inclusion) | No items below 2.0 | All items above 2.5 | All items above 3.0 |
The Honest Closing
Ninety days is enough to build the system. It is not enough to perfect it.
The founder who completes this protocol will have a studio that functions differently from the one they started with. Artisans will be making independent decisions they previously escalated. Work will be flowing through at least two documented handoff points without the founder’s involvement. Every high-value piece will be leaving the studio with a verified provenance record that belongs as much to the artisan who made it as to the client who commissioned it. The measurement data will show movement — not completion, but direction.
That founder will also have a studio that is in the early stages of something that takes years to complete. The habit routines are working but not yet automatic — Lally et al. (2010) put the mean at 66 days and the range at 254. The empowerment climate is improving but the team potency scores are still catching up to the individual scores. The founder’s identity transition is underway — the behavioural signature count is lower than it was at Week 1 — but the identity work is not finished. These are not failures. They are the honest description of where 90 days gets you.
Ichniowski, Shaw, and Prennushi (1997) demonstrated that the performance returns of a bundled HR system take time to materialise — the steel mills in their study showed the full productivity differential only after the complete system had been operational long enough for the complementarity effects to compound. The CCF’s 90-day protocol produces the complete system. The compounding is what happens next — in the quarterly measurement cycles, the annual routine audits, the succession readiness assessments, and the daily bench decisions that the system increasingly makes possible without the founder’s presence.
The folder that stayed on the shelf failed not because of bad science but because it was a single intervention — a seminar, a system, a conversation — deployed in isolation and expected to produce a systems-level result. The CCF is a system deployed as a system. That is the only thing that changes the outcome. And now you have the week-by-week protocol to build it.
Frequently Asked Questions
1. I completed the 90 days but my Week 12 empowerment scores are only marginally higher than Week 4. Has the protocol failed?
Marginal improvement at Week 12 is not protocol failure — it is the expected result of a system that has been operational for eight weeks since the first measurement. Seibert, Wang, and Courtright (2011) reported a meta-analytic correlation of ρ = .44 between empowerment and performance — a strong effect that takes time to manifest in measurement scores, particularly at the team level. The more diagnostic question is not the absolute delta but the direction and the subgroup variance. If all dimensions are improving, even marginally, and no subgroup is declining, the system is working at the expected rate. If any dimension is declining or any subgroup is worsening, that is the signal requiring attention. Compare your Week 12 results to the 12-month milestone framework and assess whether you are on the expected trajectory for Month 3 targets — not whether you have already reached Month 6 targets at Day 90.
2. My December peak season begins in Week 6 of the protocol. Should I delay the start or push through?
Neither. Restructure the timeline. The implementation dip and the production peak should not coincide — the combined pressure is the most reliable trigger for the Dip Misread failure mode. The practical recommendation: begin the protocol no later than sixteen weeks before your peak season begins, which gives you thirteen weeks of protocol plus three weeks of buffer before peak pressure arrives. If your peak is eight weeks away, complete Weeks 1 through 3 now — the Foundation Phase creates no production disruption — and pause the protocol at the end of Week 3. Resume from Week 4 immediately after the peak concludes. The Safety Pre-Flight and Identity Bridge work done in Weeks 1–3 will not degrade during a four-week pause; the empowerment climate will hold. Do not attempt Pillar Activation during peak season in your first implementation cycle.
3. Two of my artisans are not engaging with the end-of-day bench reviews. They participate but contribute nothing substantive. What do I do?
This is the Edmondson (1999) psychological safety deficit made visible. Non-substantive participation — presence without contribution — is the most common early indicator that the Safety Pre-Flight has not yet produced a sufficient climate for interpersonal risk-taking. The response is not to press those two artisans for more contribution — that pressure increases evaluation apprehension and produces less honest participation, not more. The response is to increase the Active Error Modelling frequency for two more weeks — specifically naming technical decisions that the non-participating artisans would have seen and could evaluate. When the master jeweller publicly names a decision that the polisher could legitimately have an opinion about, and asks that polisher “what would you have done?” — the invitation is specific enough to be answerable without requiring the artisan to volunteer a position they have not been asked for. Nembhard and Edmondson (2006) found that direct, specific invitations to contribute are significantly more effective at activating voice in low-status team members than open-ended invitations to anyone who wants to speak.
4. My senior setter is performing the Digital Passport routine correctly but the apprentices are entering incomplete records. How do I address this without making it a disciplinary issue?
Incomplete records from apprentices are almost always a competence gap rather than a compliance gap — the apprentice does not know what constitutes a complete record for the type of work they are handling. The response is a 20-minute one-on-one coaching session between the senior setter and each apprentice, reviewing the record template against a completed example. Frame the session explicitly: “I want to show you what a complete record looks like for this type of piece, because the record is your proof that you made this — and you want that proof to be complete.” This framing activates the Jiang and Cheng (2025) meaning mechanism — the record as professional portfolio — rather than the compliance mechanism. If incomplete records persist after two coaching sessions, investigate whether the apprentice understands the meaning framing from the Week 9 conversation or whether they experienced the Passport introduction as a monitoring system despite the framing. If it is the latter, repeat the Transparency Equity conversation individually with that artisan.
5. After the 90 days, how do I know when the system is mature enough to begin the exit multiple conversation with a potential buyer or successor?
The system is ready for the exit multiple conversation when four conditions are simultaneously true. First, the founder has been absent from the studio for five consecutive production days without the team’s performance or quality standard materially declining — verifiable through the job completion rate and any client feedback during that period. Second, at least three complete commissions have been delivered to clients from brief to delivery without the founder’s direct involvement in any bench decision. Third, the Week 12 empowerment scores show improvement above Week 4 baseline across all subgroups — not just the senior cohort. Fourth, all active Digital Passport records are complete and the physical-digital binding has been verified for the most recent quarter’s pieces. These four conditions together constitute the operational proof of systems-dependency that distinguishes a 6 to 7 times EBITDA multiple from a 3 to 4 times one. Before all four are met, the conversation is premature — not because the trajectory is wrong, but because the evidence base for the higher valuation is not yet assembled.
References
Adler, P. S., & Borys, B. (1996). Two types of bureaucracy: Enabling and coercive. Administrative Science Quarterly, 41(1), 61–89.
Chen, G., Kirkman, B. L., Kanfer, R., Allen, D., & Rosen, B. (2007). A multilevel study of leadership, empowerment, and performance in teams. Journal of Applied Psychology, 92(2), 331–346.
De Filippi, P., & Wright, A. (2018). Blockchain and the law: The rule of code. Harvard University Press.
Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.
Feldman, M. S., & Pentland, B. T. (2003). Reconceptualizing organizational routines as a source of flexibility and change. Administrative Science Quarterly, 48(1), 94–118.
Frey, B. S., & Jegen, R. (2001). Motivation crowding theory. Journal of Economic Surveys, 15(5), 589–611.
Ibarra, H. (1999). Provisional selves: Experimenting with image and identity in professional adaptation. Administrative Science Quarterly, 44(4), 764–791.
Ichniowski, C., Shaw, K., & Prennushi, G. (1997). The effects of human resource management practices on productivity: A study of steel finishing lines. American Economic Review, 87(3), 291–313.
Jiang, H., & Cheng, X. (2025). Perceived algorithmic control and gig workers’ work engagement: Assessing the mediating role of psychological empowerment. Frontiers in Psychology. PMC.
Kirkman, B. L., & Rosen, B. (1999). Beyond self-management: Antecedents and consequences of team empowerment. Academy of Management Journal, 42(1), 58–74.
Lally, P., van Jaarsveld, C. H. M., Potts, H. W. W., & Wardle, J. (2010). How are habits formed: Modelling habit formation in the real world. European Journal of Social Psychology, 40(6), 998–1009.
Milgrom, P., & Roberts, J. (1995). Complementarities and fit: Strategy, structure, and organizational change in manufacturing. Journal of Accounting and Economics, 19(2–3), 179–208.
Nembhard, I. M., & Edmondson, A. C. (2006). Making it safe: The effects of leader inclusiveness and professional status on psychological safety and improvement efforts in health care teams. Journal of Organizational Behavior, 27(7), 941–966.
Petriglieri, G. (2011). Under threat: Responses to and the consequences of threats to individuals’ identities. Academy of Management Review, 36(4), 641–662.
Repenning, N. P., & Sterman, J. D. (2002). Capability traps and self-confirming attribution errors in the dynamics of process improvement. Administrative Science Quarterly, 47(2), 265–295.
Seibert, S. E., Wang, G., & Courtright, S. H. (2011). Antecedents and consequences of psychological and team empowerment in organizations: A meta-analytic review. Journal of Applied Psychology, 96(5), 981–1003.
Spence, M. (1973). Job market signaling. Quarterly Journal of Economics, 87(3), 355–374.
Spreitzer, G. M. (1995). Psychological empowerment in the workplace: Dimensions, measurement, and validation. Academy of Management Journal, 38(5), 1442–1465.
Walch, A. (2019). Deconstructing “decentralization”: Exploring the core claim of crypto systems. In C. Brummer (Ed.), Crypto assets: Legal, regulatory, and monetary perspectives. Oxford University Press.
Wood, W., & Neal, D. T. (2007). A new look at habits and the habit-goal interface. Psychological Review, 114(4), 843–863.
