The first thirty days: understand before you act
Step 1 / 2·The prove-yourself-early trap
0/2 steps done
Learning objectives — after this module you will:
- Understand why proving yourself too early backfires
- Map your stakeholders in week one
- Ask the questions that build context fastest
The prove-yourself-early trap
Avoid the commonest new-joiner mistake.
New joiners carry a self-imposed pressure: to show they are worth it, as fast as possible. That pressure produces a proposal in week two, before they know why things are done the current way.
The problem is not that the proposal is wrong. Many new-joiner proposals are technically sound. The problem is that they usually miss a constraint the insiders already know about — and a proposal that misses a constraint makes the room conclude you do not understand the work, however good the rest of it is.
Thirty days spent understanding is not thirty days wasted. It is the investment that gives every later proposal weight.
The same proposal, two moments
Week 2
“'Four approval levels is too many; we should cut it to two.'”
The room knows level three exists because of an incident last year. Their conclusion: this new person wants to change things before understanding them.
Week 6
“'I understand the third approval level was added after the incident last March. If we build that check into step two, we keep the control and lose a round. What risk am I not seeing?'”
Shows you know the history, preserves the control objective, and invites insiders to add what you missed. Same proposal, completely different reception.
The question that unlocks any context
'How long has it been done this way, and what did you do before that?' It almost always produces the story that explains why things are as they are.