Transitions — The First 90 Days and the New Lead's Political Surface

Master the two transition scenarios where political stakes spike: joining a new organization (the cold-start problem) and stepping into a lead role (the phase shift). Build the first-90-days political plan for your next real role, and — if you lead — the written operating stance that resolves the credibility paradox. Cold-starting into an organization is cold-starting into a running system: read before you write, map dependencies before you change them, build trust capital before you spend it. The first 90 days are the bootstrap phase; the topology you build in this window determines what you can do in months 4-24. The lead role is the ApplicationController. The lead who tries to be the whole controller — every action method themselves — fails the way an over-stuffed controller fails: bottleneck, brittleness, no separation of concerns, team velocity grinding through one chokepoint. The lead who refuses all controller logic fails the way an app with only models fails: no orchestration, dropped and duplicated requests, incoherent user-facing behavior. The literate lead handles cross-cutting concerns at the right boundary (advocacy, sponsorship, conflict, narrative — the team's auth/error-handling/logging layer), delegates action-specific work, and keeps writing just enough action methods — the architectural ones — to retain the judgment the cross-cutting work depends on. The ratio is dynamic; refactor it explicitly every 3-6 months. The team will tell you, in velocity and morale, when it's wrong.