The symptom
You want more initiative around you. Proposals don’t arrive, or they arrive and die.
The signal
“What happened to the last person who proposed something here?”
What is going on
A team doesn’t run on stated values. It runs on observed consequences. People are excellent statisticians of how you react. Nobody remembers the slide. Everybody remembers what happened to the person who tried.
Which is why passivity reads wrong from the outside. You see a team with no initiative. The team remembers an edit that got reverted without explanation three months ago.
The objection is fair, so take it. Not everything comes from the organisation. A missing access, a week already full, a skill that isn’t there yet, a damaged relationship between two people: these combine. Assigning a cause before looking at one real case gets you nothing. Look at the case. Not the label on the person.
What doesn’t get excused is the pattern. If the last four proposals ended in the same place, that isn’t a bad week. That is the thing you built.
If you don’t run the team, you are not required to rebuild the organisation alone. Asking a question, making a constraint visible, proposing a trial: that is already acting. A private conversation often travels further than a confrontation in a meeting. You don’t have to spend status to prove commitment.
Changing the rule isn’t enough either. People wait to see how the first initiative gets received. That one counts more than the announcement.
What to check
Look at the last three proposals made in your team. Not the last three you liked. The last three.
What happened to each one, and how fast? Who got an answer, who didn’t?
Then pick a change small enough that you will actually hold it: clarify a mandate, open an access, reserve time, answer within two days. Escalate what sits above your role.
After a real chance to practise, look at whether anything moved. If the trial never happened, the constraint is your answer.
From where you sit
- Engineering: name the dependency that blocks you before talking about a lack of autonomy.
- Support: bring one case where a proposal got a follow-up, and one where it didn’t.
- Management: say what you can decide alone and go get a ruling on the rest.
- Recruiting: separate what is learning, what is working conditions, and what is the role.
To discuss
Which useful proposal died here without an answer, and what did the team conclude from it?