Not every consequential transition starts with someone walking through the door for the first time. Sometimes it's an existing leader stepping into a different role, or an existing board finding its footing with someone new at the helm. In each case, a working relationship between a leader and a board is forming or changing, and that relationship deserves deliberate attention rather than assumption.

This offering is deliberately narrow: focused, facilitated work on the board relationship itself, not full-scale transition management. It's built for moments like:

• A long-tenured internal leader stepping into a new relationship with a board that already knows them

• An externally hired leader who needs to build trust and shared understanding with an established board quickly, rather than over years

• A founder-led organization moving to its first non-founder leader, where the board-leadership relationship has never been formalized

• An interim leader and board aligning explicitly on scope and decision rights for a bridge period

• A new board chair building their own working relationship with the CEO or president and the rest of the board

In each case, the work centers on facilitated conversations that surface what the board and the leader need from each other, addressed early rather than left to assumption.

This work is people-focused, not a rigid set of deliverables imposed from outside. I think of the role as administratively creative: building the systems, protocols, and processes that clear the operational brush so leaders and their teams can stay focused on the work that actually makes change happen. Every recommendation is shaped around how a specific team already operates, and nothing is finalized without input from the people who will actually use it.

• End-to-end workflow mapping and friction-point identification

• Team structure and role clarity, sorting out who owns what before adding new systems on top

• Capacity and workload assessment across a team or function

• Discovery built on direct interviews and observation, not assumptions about how work "should" happen

• Checklist and protocol design for recurring, high-stakes tasks

• Documentation and institutional knowledge capture, so process lives outside any one person's head

• Onboarding frameworks for new team members

• Meeting and communication cadence design, cutting noise so decisions move faster

• Tool and platform evaluation, fitting systems to how the team already works rather than the reverse

• Change management and communication planning for rolling out new systems