yashovardhan

Tribe

Tribe: one place for briefs, tasks and talk between brands and teams

Product
Tribe
Year
2023
Industry
Internal tool
Contributors
Debasmita K., Anish K., Bhargav R., Anuj G., Anshuman G., Berkha K., Smith S., Dhruv P.
Tribe case study cover

Results

Faster project turnaround
40%
Less time spent searching for updates
50%
Fewer unanswered messages
60%

Context

Every project lived in four apps

At Terribly Tiny Tales, client work was split across WhatsApp, Slack, email and Google Chat. In interviews, 80% of delays came from fragmented communication. Chat tools were bad at tracking and project tools felt heavy, so I designed Tribe, a chat-first tool with tasks and approvals inside the conversation, with a team of eight.

01Briefs

Getting the brief right

A brief builder where every requirement is entered, assigned and reviewed, with members shown by role and live status.

Why: A lot of confusion started at the brief, so members, tasks, files and chat all hang off it.

Tribe: Brief builder. Every requirement entered, assigned and reviewed in one view, references attached.Tribe: Brief builder. Every requirement entered, assigned and reviewed in one view, references attached.
1.1Brief builder. Every requirement entered, assigned and reviewed in one view, references attached.
Tribe: Members under a brief, with accepted role and live status.
1.2Members under a brief, with accepted role and live status.

02Tasks

Breaking it into tasks

Tasks with owners, deadlines and deliverables, and side panels for quick reassigning.

Why: Creative projects change hands a lot.

Tribe: Deadlines, assignments and deliverables together. Side panels for reassigning.
2.1Deadlines, assignments and deliverables together. Side panels for reassigning.
Tribe: A single task: files, owner, collaborators, deadline.Tribe: A single task: files, owner, collaborators, deadline.
2.2A single task: files, owner, collaborators, deadline.

03Files

Files

Script, voiceover, animation and packaging grouped by type, each with uploader, tags and approval status.

Why: Nobody should have to scroll back through chat for the latest voiceover.

Tribe: Script, voiceover, animation and packaging, each with uploader, tags and approval status.
3.1Script, voiceover, animation and packaging, each with uploader, tags and approval status.

04Chat

Keeping the talk next to the work

Threads live beside the task they're about, timestamped and role-tagged.

Why: Everyone already lived in chat, so we gave it structure instead of replacing it.

Tribe: A thread, timestamped and role-tagged.
4.1A thread, timestamped and role-tagged.
Tribe: Task chat beside the files, task details and collaborators.Tribe: Task chat beside the files, task details and collaborators.
4.2Task chat beside the files, task details and collaborators.

Outcome

What changed

Hiring for product design, or building something new? Send the context and we can talk it through.

Book a 30-min call (opens in new tab)