Running a focused completion session across family enterprise teams

Built on Speed of Implementation by Richard C. Wilson.

A focused completion session can finish an enterprise project that keeps losing attention to ordinary business. The family owner should choose a defined result and give the team the resources to deliver it. Gathering employees in a room without resolving their dependencies usually creates another meeting.

Module 4 of Speed of Implementation describes concentrating work on a single project, with preparation before the session begins. For a billionaire family enterprise, I would use that approach for work that is understood and authorized. The session should produce something an operating manager can accept and use.

Choose a result that fits the session

Select a project whose remaining work is sufficiently clear. Preparing a customer service handbook from agreed procedures may fit. Settling a major disagreement about the business model probably requires a different conversation before anyone can execute.

Define what completion means to the person receiving the result. A file that exists but cannot be used by the service team is unfinished. The receiving manager should identify the acceptance conditions before people reserve their time.

Make the scope small enough to complete without pretending that important checks are optional. Work that depends on an unavailable supplier or specialist is not ready simply because the owner wants it done.

Prepare the materials and permissions

The book puts preparation before concentrated execution. Confirm that the team has the relevant records and access to the systems it will use. Have someone test those arrangements ahead of time. Discovering that only an absent employee can open the source file wastes the shared session.

Ask the responsible managers to release the participating employees from conflicting work. A senior owner cannot assume that a calendar invitation has resolved customer obligations. Identify who will handle urgent operating matters while the session takes place.

Keep access proportionate to the task. Concentration does not require everyone to see unrelated family or company information. Prepare a working set that contains what participants need.

Assign responsibility by the work

Give each participant a piece of the deliverable that matches their knowledge. The person who understands the process should be available to answer substantive questions. A coordinator can keep the work moving, but cannot replace missing operating judgment.

Agree how pieces will be combined. When several employees use different assumptions or formats, reconciliation can consume the entire session. A shared example of acceptable output often prevents that problem better than a long instruction document.

Identify who resolves disagreements within the approved scope. Escalate questions that would change the scope or exceed the session's authority. Speed should not leave the newest employee guessing what the founder would approve.

Protect concentration without hiding problems

Limit ordinary interruptions and give people time to finish connected work. Keep a route for a genuine business emergency. The session's purpose does not justify ignoring an existing obligation that requires immediate attention.

Let participants raise a dependency as soon as they find it. A team that fears reporting a problem may fill the gap with an assumption. The resulting deliverable can appear complete while containing an error that will emerge only when someone uses it.

Accept the result before dispersing

Have the receiving manager inspect the work against the agreed conditions. Use an actual task to test whether the result is usable. If corrections are needed, distinguish a contained fix from a fundamental misunderstanding of the assignment.

Record any remaining work with a responsible person. Avoid calling the session complete if the final handoff is still missing. The family needs an accurate account of what became operational and what remains a dependency.

Keep what the session taught

Afterward, note which preparation helped and which missing input caused delay. Apply that information when deciding whether another project suits concentrated work. The same session design will not fit every operating problem.

A useful completion session leaves fewer unresolved tasks in ordinary business. If it repeatedly generates new lists without producing accepted work, narrow the scope or resolve the underlying decisions before holding another one.

Questions and answers

Should the family founder attend throughout? Only if the work requires that involvement. The founder's role should be specified alongside everyone else's.

What makes a project ready? A defined result, available inputs, clear authority, and someone capable of accepting the finished work.

This page is general information, not legal advice. Family governance documents and dispute processes should be reviewed by a qualified attorney.