What I want a team to be able to count on
By Gyata Tabiri · Revised October 30, 2026
I want the people around me to know what they can expect from my contribution: attention to the assignment, a clear explanation when something needs discussion, and a practical way forward.
Be clear about the contribution
A focused assignment can be valuable without ownership of the whole project. I am comfortable building from an approved design and helping with the wider work when the team needs it. Understanding the boundary makes it easier to know when to act and when to bring someone else into the decision.
Raise the issue in a useful form
In email work, I have explained implementation problems through screenshots, writing, and conversations. That gives the designer a basis for a revision. It is more constructive than silently changing the design or treating a constraint as someone else’s mistake.
Keep people’s work visible
At Edgewood, the work involved colleagues responsible for design, content, and coordination. Keeping those contributions visible gives a more useful account of how the projects came together. The same care matters in the handoff: people need to know who owns a decision and where to take a question.
Leave the next person a way forward
Clear files, a decision note, and an honest explanation of what was tested help a teammate continue the work. Those details are modest, but they are part of what makes someone dependable to work with. They are also useful topics for an interview or reference conversation.
A hiring conversation can explore those habits through the work itself. I can discuss the decisions around a build or a revision, alongside the finished piece, so the team can understand how I would contribute.