Rigid job descriptions quickly become obsolete. I use an exploratory approach centered on regular check-ins where employees share progress, ask questions, and surface support needs. These sessions reveal true goals, highlight bottlenecks, and refine workflows. Over time, vague roles turn into measurable outcomes. The cycle ensures accountability is based on real work, enabling teams to scale with clarity and speed.

---

In a fast-moving company, roles often evolve faster than we can document them. The ideal scenario is that every job is fully defined before hiring, complete with a job description, KPIs, and detailed goals. In reality, many roles start with a template or a set of assumptions that get backlogged or later scrapped once the real demands of the role come into view.

Through experience managing people across different levels, I’ve found that front-loading too much detail rarely works. Instead, I use an exploratory approach that establishes oversight, accountability, and performance clarity over time.

The foundation of this process is the alignment meeting. These are scheduled check-ins with direct reports where they share their achievements, raise questions, and ultimately answer the most important prompt: how can I help you? The purpose is to surface progress, remove obstacles, and stay in lockstep as responsibilities evolve.

With employees at Level 5 and below, alignment meetings happen daily or every other day. For Level 6 and above, weekly check-ins suffice. These aren’t just status updates, they’re working sessions where we track progress, uncover bottlenecks, and gradually clarify what measurable outputs should look like.

For example, one of my leaders recently took ownership of updating our Kaamfu product documentation. At first, the goals were vague. After a few alignment meetings, it became clear that the true measure of success would be the 500 product documents needed before launch. His initial pace was too slow to hit the three-month deadline, so together we drilled into the work, created a repeatable template, and set a new cadence of 1–1.5 hours per document. This gave us both visibility and confidence in the delivery plan.

Over time, this process has become repeatable across roles:

1. Start with a generic, targeted JD. Enough to orient the hire, but not overly prescriptive.
2. Assign work to establish cadence. Early deliverables help reveal natural velocity.
3. Schedule regular alignment meetings. Daily or weekly, depending on role level.
4. Surface measurable goals. Let patterns emerge from real work, not assumptions.
5. Refine goals through coaching. Drill into workflows, remove friction, and revise targets.

The result is a simple but powerful cycle: hire → align → measure → refine. It not only builds accountability but also ensures that goals are rooted in the actual dynamics of the role, not in outdated job templates. This exploratory process has consistently helped me transform vague responsibilities into clear, measurable outcomes and build teams that can scale in sync with the company.

…