From clouds to stones: how goals evolve into action

When I lead, I spend most of my time working in the Crownline space of evolving ideas where rigid plans kill momentum. I’ve learned that forcing vague, high-level goals into fixed task lists too soon suffocates my creativity and slows progress. That’s why I built the WorkControl model that lets goals stay fluid like clouds, evolving with new information, until they naturally harden into clear, actionable tasks-what I call stones. This structure gives me the freedom to adapt and experiment while ensuring my team has the clarity they need to execute, all tied together by visible commitments.


If you lead a business, a team, or even your own career, you’ve probably lived this pattern: At the highest level—what I call the Crownline—everything feels amorphous. Your job is to observe, explore, and think. You’re mapping terrain, adjusting direction, and constantly searching for the next move. But eventually, those thoughts—those big-picture ideas—have to crystallize. That’s where goals come in—and where the real work begins.

Goals are clouds. They float. They evolve. They’re intentionally vague at first. And they have to because when you’re leading from the Crownline, rigidity is your enemy. You need room to change your mind, pivot priorities, or reshape your vision as new information comes in.

I’ve always felt stifled when I’m forced to cram my evolving goals into a rigid, bullet-point list. It doesn’t work because I know those goals will change. I know they’ll merge, split, vanish, or shift direction as I learn. But the rigid rules of a task list are hostile to that kind of change. They demand locked definitions—who’s doing what, when, and how. And when that structure gets applied too early to evolving ideas, it kills momentum. Defining those details isn’t my role—and frankly, it shouldn’t be. My job is to set direction, then hand implementation to my managers.

That freedom to evolve is essential at the top, but dangerous at the frontline. That’s why organizations need a system to connect clouds to earth—without suffocating the natural creative process. In the WorkControl model—the framework I’ve been developing my entire career (workcontrol.org), I make that connection by superimposing a Goals Structure onto the rigid world of tasks. It works like this:

  • ✅ Every worker has a Goals Panel, where they can define personal or assigned goals.
  • ✅ Crownline leaders set broad, directional goals like “Scale the company,” “Deliver the product,” “Build secure systems.”
  • ✅ Those high-level goals descend down to the next level, where they get clarified, refined, and nested into sub-goals and eventuall tasks.
  • ✅ As the structure evolves, goals harden. What starts as a floating, amorphous goal eventually consolidates into actionable, measurable tasks.

The primary difference between goals and tasks is how fluid they are—how easily they can be moved, changed, or restructured. You can add a new goal at any time, even on top of an existing stack of goals or active tasks. You simply create it and connect it—it’s designed to evolve. Tasks, on the other hand, are more rigid. They carry structure, ownership, and often active progress. You can—and should—refine overarching goals while tasks are underway without disrupting day-to-day execution. Changing tasks midstream is harder, and intentionally so. That doesn’t mean you never stop or adjust a task in progress—sometimes you have to—but more often, new goals emerge while work is ongoing, shaping future direction without derailing current operations.

There’s one constant across both layers: Commitments.

Every goal, no matter how fluid, still carries a commitment. It might be vague, evolving, or low-confidence at first, but there’s always some promise that someone, somewhere, is pushing it forward. That same principle applies as goals harden into tasks. Tasks carry more rigid commitments with clear deliverables, deadlines, effort estimates. But the foundation is the same:

  • ☁️ Clouds with commitments — High-level goals evolving, but still backed by ownership.
  • 🪨 Stones with commitments — Hardened tasks defined by clear expectations.

Commitments vary. Their confidence level, scope, and deliverables shift as the work evolves. Early-stage goals may only carry directional commitments: “I’ll explore this,” or “We’re pursuing this outcome.” As goals descend and crystallize, those commitments solidify: “We’ll deliver this feature,” “This report is due by Friday,” “This task belongs to this person.”

This entire structure directly corresponds to the level of clarity within an assignment. Goals are often assigned with vague, incomplete, or intentionally undefined outcomes. That isn’t a flaw—it’s by design. In many cases, clarity itself is the deliverable. A Crownline leader may assign a broad goal with the expectation that the assignee will help shape, define, and evolve it into something actionable. But that only works when the person receiving the goal has the capability to interpret ambiguity and convert it into meaningful action. If unclear goals are passed down to the frontline or even to midline employees who lack that skill, the system breaks. Either the supervisor has failed to translate the vision into appropriately scoped deliverables, or they’ve overestimated the assignee’s ability to operate in the unknown. Both issues surface quickly—and the solution is the same: goals must descend with increasing clarity until they harden into actionable stones.

Different Structures for Different People

This separation—clouds for goals, stones for tasks—is intentional. By defining them differently, we allow different people to define work in the way they naturally operate.

As the CEO, I operate at the Crownline. And while I want my workers to execute clearly defined tasks, the truth is, most of the time, I don’t know exactly what I want upfront. I know the general direction—we need to scale, we need to improve security, we need to build—but the specifics evolve over time. I need space, feedback, and sometimes experimentation to figure it out.

That’s why the cloud-like Goal Structure matters so much. It allows me to work the way I actually think:

  • ☁️ An open canvas of floating ideas.
  • ☁️ A mind map of disconnected pieces.
  • ☁️ Fragments of the bigger puzzle I’m still assembling.

Many of those clouds don’t connect yet—and that’s fine. I’m building the vision in real time. I’m thinking, learning, reshaping. Some clouds will merge, others will disappear. New ones appear every day as I adapt. This system lets me evolve our organizational goals, track the effort happening under them, and track the commitments tied to them. Even when goals are shifting, there’s always clarity on who owns the next step forward.

You would never rescope a task too much. Tasks need rigid definitions of assignees, deadlines, effort estimates, and accountability. But goals? Goals shift, split, change, and evolve all the time. Their commitments evolve with them, starting vague and becoming more specific as we learn and clarify.

And that’s healthy as long as those changes are visible, captured on a timeline, and everyone involved sees them happen. I don’t have to recreate everything every time I pivot. I just adjust the clouds, update definitions, evolve commitments, and we move forward.

The hardened, rigid rules of tasks simply don’t apply to goals, but both require commitment.

The Natural Cycle: Clouds Become Stones

At its core, building anything—whether it’s a company, a product, or a team—is a cycle of evolving thought into concrete action. You rarely start with perfect clarity. You start with an idea, a direction, maybe just a gut instinct. That idea floats for a while. It changes. You test it, reshape it, get feedback, adapt. Over time, it hardens—it becomes structured, actionable, and specific. This is the natural rhythm of execution. You move from clouds to stones. The WorkControl model formalizes that process. It gives space for goals to remain fluid when they need to be and ensures they harden at the right moment, with the right commitments attached.

This is the natural cycle of building:

  • ☁️ Clouds — Flexible, evolving goals, mapped on an open canvas.
  • ➡️ Conversion — Collaboration, feedback, restructuring as clarity emerges.
  • 🪨 Stones — Hardened, actionable tasks ready for execution.
  • Commitments at every stage — Evolving promises that tie both layers to real outcomes.

Leaders keep the freedom to adapt. Workers get the clarity to execute. Everyone understands the commitments—whether they’re soft directional ones or hard deadlines. That’s how we connect the creative chaos at the top with the operational discipline at the front.

Simply put: Goals are soft clouds. Tasks are rigid stones. Commitments hold them all together, and the WorkControl model brings them into alignment.

Every organization is in the race to autonomy

Autonomization is not a distant future. The race is on, and the organizations preparing today will be the ones that win tomorrow.

Join my newsletter

Industry news is everywhere. Join my newsletter for practical insights on what to prioritize inside your organization to be ready for what’s happening.