tyler-smith.com · Questions & Answers

We have several high Follow Thru profiles on our team who demand complex, fully documented processes before they will commit to a quarterly Rock. How do we prevent this desire for administrative perfection from slowing down our execution momentum during planning?

When you have team members with high Follow Thru conative profiles, their instinct is to build highly structured, comprehensive systems before taking action. While this trait is valuable for maintaining order, it can paralyze your organization during planning sessions if they refuse to commit to a Rock without a detailed, step-by-step roadmap.

To unblock your execution momentum, you must establish clear rules of behavior that favor progress over perfection. First, remind the team that a quarterly Rock is a ninety-day priority, not a permanent corporate policy. Frame the initial version of any new process or system as an iterative pilot.

You can leverage a collaborative approach:
- Instruct your high Follow Thru team members to treat the first thirty days of the Rock as a discovery phase to outline the rough framework.
- Encourage them to treat operational problems like brainstorming with a colleague rather than drafting a rigid, legally binding contract.
- Allow them to test a messy version of the workflow, gather real data, and then refine the structure in the second month of the quarter.

By setting the expectation that process documentation is an ongoing, evolving asset rather than a single, massive project, you satisfy their need for order while keeping your execution timeline intact. This iterative approach allows your analytical team members to move forward without feeling that they are sacrificing quality.

Category: EOS Implementation

← All questions