Un espacio de trabajo para la colaboración en equipo

Teams tracked delivery on the board, wrote specs and notes in Spaces or a wiki, and opened generic chat when they needed help. Context did not carry across. Assistant threads were ephemeral. Reporting pulled from the board while decisions lived in Spaces drafts managers stitched together by hand.

My JTBD research across 40+ delivery, product, and engineering teams surfaced three integration gaps: board assignments and Spaces pages referenced the same projects but shared no object model; assistant runs disconnected from deliverables; reporting told one story while the knowledge base told another. Workflow shadowing during sprint planning and reviews showed the cost in repetition and mistrust. Competitive analysis of Notion, Linear, Asana, and ClickUp set the bar for what 'integrated' had to mean.

Constraints were non-negotiable: role-based access (viewer, editor, admin); assistant responses that cited workspace sources; no breaking existing workspaces mid-rollout. Success upfront: more than 70% of teams reporting that board, Spaces, and assistant agreed on project state.

I designed end to end on a shared shadcn Maia system with role-based access. Three directions were on the table. Keep separate surfaces with manual links between them: rejected, because it perpetuated context switching. Embed docs inside board cards: rejected, because it trapped knowledge inside board hierarchy. Shared workspace object model where boards, Spaces, and assistant all referenced the same projects, tasks, and people: what I shipped.

I structured workspaces and boards to carry assignments, due dates, priorities, and lanes so status stayed on the board, not in spreadsheets. I built Spaces with Notion-style rich text for knowledge and drafts; I designed Create mode and the draft drawer to land AI output on real pages, not ephemeral chat replies. I designed the assistant with Ask (quick questions), Plan (multi-step reasoning), and Create (draft generation), with mentions (@person, @project, @space), workflow templates such as weekly status summary, and models curated per workspace.

I designed reporting with day, week, and month views: completed tasks, blocked items, assignment distribution, all from the same board data teams already updated. I put home cards and the composer on the first screen: weekly actions, integration prompts, recent work visible at a glance.

I validated in the field, not in a deck. Twenty teams ran a three-month beta. Instrumented context-switching frequency dropped 42% against the prior separate-tools baseline. Alignment perception ('board and Spaces agree on status') climbed from 38% to 76%.

Teams stopped treating the board, knowledge base, and chat as three competing truths. Fewer reviews opened with a recap nobody had time for. Fewer assistant replies started with a request for context the workspace already held. Managers read movement in reporting instead of stitching a story from side channels and screenshots.

Because I designed Create mode to land drafts into Spaces with citations to board tasks and existing pages, teams edited and shipped assistant output instead of discarding it — 78% reported 'board, Spaces, and assistant share the same truth', exceeding the 70% target, which underpinned beta retention and paid-seat expansion conversations (directional; specific revenue figures under NDA).