What I want a team to be able to count on
By Gyata Tabiri · Revised November 2, 2026
I think trust grows in the ordinary moments: an issue raised before it becomes a surprise, a decision explained without dismissing someone else’s work, and a file another person can continue without guessing.
Make the boundary useful
A focused assignment does not require control of the whole project. I am comfortable building from an approved design while paying attention to the wider work. Knowing what I own also helps me recognize when a decision belongs with a designer, content colleague, or approver.
Bring the problem with enough context
In email work, I have used screenshots, writing, and conversations to explain implementation issues. The designer could then revise the work. I prefer that exchange to a silent change: it lets the person responsible for the design understand the constraint and contribute to the answer.
Keep other people’s contributions visible
The Edgewood work involved colleagues across design, content, marketing, and technical responsibilities. A useful account of a project should leave room for those contributions. It should be possible to describe my part clearly without suggesting that a shared result came from one person working alone.
Leave uncertainty in a form someone can act on
“Not checked yet” is useful when it identifies the missing check and who needs to complete it. It is much less useful as a vague warning after a file has been handed over. I want the distinction between completed work and open questions to remain understandable.
Dependability is often quiet. It is the difference between receiving a file and knowing what you can responsibly do with it.
Read alongside: Explaining a concern without taking over the answer · Making the handoff specific.