مساحة عمل واحدة لتعاون الفريق

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. Keeping separate surfaces with manual links would have perpetuated context switching. Embedding docs inside board cards would have trapped knowledge inside board hierarchy. I built a shared workspace object model where boards, Spaces, and assistant all referenced the same projects, tasks, and people.

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.

Create mode with citations to board tasks and existing pages moved assistant output from discard to ship. Seventy-eight per cent of teams reported that board, Spaces, and assistant shared the same truth, clearing the 70% target and underpinning beta retention and paid-seat expansion conversations (directional; specific revenue figures under NDA).