At Dellecod, we’ve come to recognize a quiet but consistent pattern — the people who shape the direction of a project or team are often not the ones with the loudest voices or the fanciest titles. Instead, they’re frequently the ones who take time to write things down.
This might seem like a small act. After all, writing meeting notes, project docs, or internal guides doesn’t always feel like leadership. It’s easy to assume that influence lives in presentation decks, bold initiatives, or executive strategy sessions. But time and again, we’ve seen that the simple habit of documenting things is one of the clearest markers of emerging leadership.
Writing creates traction. It brings structure to a conversation, especially in the fast-moving world of software where ideas can fly in every direction. When someone captures a decision, outlines a process, or proposes the next steps in writing, they’re shaping the narrative — not just recording it. They’re creating a shared reference point that others return to. And that has real power.
What’s surprising is how few people actually do this. In most companies, it’s rare to find someone who consistently writes things down. There’s often an unspoken assumption that someone else will do it — some undefined "note taker" or "operations person" whose job it is to keep track of things. But when someone volunteers to take that on, especially without being asked, it signals something bigger. Initiative. Care. A sense of ownership.
We’ve noticed that people who document things tend to rise. Not right away — this isn’t a shortcut to promotion or a substitute for technical skill. But over time, their influence grows. Others begin to turn to them for clarity. Stakeholders take their input more seriously. Their names show up more often in internal conversations, not because they ask for recognition, but because their writing makes things better.
That’s the quiet superpower of writing: it gives weight to your ideas. It makes your thinking visible and testable. It surfaces your ability to navigate complexity, to bring coherence where there's ambiguity. In tech, where so much depends on clear communication across teams and time zones, this skill compounds.
It’s also telling how writing can serve as a signal. In hiring or cross-functional work, one of the patterns we watch for is who tends to write things down. In younger employees or new team members, this behavior often predicts later leadership. It’s a simple but meaningful way to spot someone who isn't just executing tasks, but starting to think at the systems level.
For us, this isn’t about instituting a note-taking culture or adding another item to everyone’s to-do list. It’s more about recognizing that writing is a form of contribution — one that isn’t always celebrated, but often has outsized impact.
So when someone on the team starts keeping a running doc of a tricky project, or drafts a thoughtful rationale before sprint planning, we pay attention. Not because it’s flashy, but because we’ve learned — over and over — that the one who writes often leads.
And usually, they already are.
This might seem like a small act. After all, writing meeting notes, project docs, or internal guides doesn’t always feel like leadership. It’s easy to assume that influence lives in presentation decks, bold initiatives, or executive strategy sessions. But time and again, we’ve seen that the simple habit of documenting things is one of the clearest markers of emerging leadership.
Writing creates traction. It brings structure to a conversation, especially in the fast-moving world of software where ideas can fly in every direction. When someone captures a decision, outlines a process, or proposes the next steps in writing, they’re shaping the narrative — not just recording it. They’re creating a shared reference point that others return to. And that has real power.
What’s surprising is how few people actually do this. In most companies, it’s rare to find someone who consistently writes things down. There’s often an unspoken assumption that someone else will do it — some undefined "note taker" or "operations person" whose job it is to keep track of things. But when someone volunteers to take that on, especially without being asked, it signals something bigger. Initiative. Care. A sense of ownership.
We’ve noticed that people who document things tend to rise. Not right away — this isn’t a shortcut to promotion or a substitute for technical skill. But over time, their influence grows. Others begin to turn to them for clarity. Stakeholders take their input more seriously. Their names show up more often in internal conversations, not because they ask for recognition, but because their writing makes things better.
That’s the quiet superpower of writing: it gives weight to your ideas. It makes your thinking visible and testable. It surfaces your ability to navigate complexity, to bring coherence where there's ambiguity. In tech, where so much depends on clear communication across teams and time zones, this skill compounds.
It’s also telling how writing can serve as a signal. In hiring or cross-functional work, one of the patterns we watch for is who tends to write things down. In younger employees or new team members, this behavior often predicts later leadership. It’s a simple but meaningful way to spot someone who isn't just executing tasks, but starting to think at the systems level.
For us, this isn’t about instituting a note-taking culture or adding another item to everyone’s to-do list. It’s more about recognizing that writing is a form of contribution — one that isn’t always celebrated, but often has outsized impact.
So when someone on the team starts keeping a running doc of a tricky project, or drafts a thoughtful rationale before sprint planning, we pay attention. Not because it’s flashy, but because we’ve learned — over and over — that the one who writes often leads.
And usually, they already are.