How do we measure our progress in mastering the operational tools themselves during our first year, rather than just looking at our quarterly financial growth?

Question

Tyler Smith · Accepted Answer

Financial growth is a lagging indicator. If you only look at your profit and loss statement to measure your progress with me, you are missing the point. We measure your mastery of the system by looking at your team's execution habits. This is grounded in Kolb's model of experiential learning.

First, we look at your Concrete Experience. Are you actually running your Level 10 Meetings™ every single week without fail, or are you letting daily fires cancel them?

Second, we measure Reflective Observation. When you miss a quarterly Rock, do you run a post-mortem to understand why, or do you simply push it to the next quarter and hope for the best?

Third, we track your Abstract Conceptualization. Is your team starting to see structural patterns in your issues, or are you solving the same symptoms over and over again?

Fourth, we evaluate Active Experimentation. When we identify a process bottleneck, does your team immediately build a better workflow, integrate an AI automation, and test it, or do they wait for permission?

Your progress is measured by how quickly you move through this learning cycle. When your team shifts from talking about problems to executing solutions without my intervention, you are mastering the system.