Akashic — basecamp.com

2/4 Product Identity +

+Jtbdminor drift

Specification

Minimize the time it takes to coordinate project information across team members and stakeholders

Reality

Increase the visibility and organization of team work across projects and time ^[▣1]

Spec says minimize time; product says increase visibility and organization.

+Descriptionaligned

Specification

Project management and team communication software that centralizes work discussions, tasks, and decisions in one place per project ^[1]

Reality

Basecamp is a project organization platform that centralizes team work into structured project spaces with built-in tools

Same core concept: project-centered work organization with integrated tools.

+Anti Goalsmajor drift

Specification

NOT a heavy Scrum or Jira process that generates overhead without progress ^[2]
NOT scattered across multiple tools like GitHub issues, Slack, and email threads ^[2]
NOT per-seat pricing or enterprise negotiation ^[3]

Reality

NOT a quick task capture tool — creating tasks requires navigating to specific projects and lists, no global quick-add visible ^[2]
NOT a real-time chat platform — communication happens through structured message boards and pings, not instant messaging ^[3]
NOT a calendar scheduling tool — the 'Lineup' shows project schedules but not personal appointments or meetings ^[4]
NOT a file storage system — files are organized within project contexts, not as standalone document management ^[5]

Spec opposes tool sprawl; product opposes quick capture and chat.

3/4 Target User +

+Roleminor drift

Specification

Software product teams at established companies ^[4]

Reality

Team lead or project manager

Spec says software teams; product says team leads/managers.

+Work Contextminor drift

Specification

Teams burned by Jira's complexity or chaos of Slack + email + spreadsheet coordination ^[4]

Reality

Small to medium teams working on multiple concurrent projects

Spec targets Jira-burned teams; product targets multi-project coordinators.

+Tech Levelminor drift

Specification

Technical

Reality

Semi-technical

Spec says technical; product says semi-technical.

+Domainaligned

Specification

Software product development and project management

Reality

Project management and team coordination

Both focus on project management; spec adds software development.

+Reading Levelminor drift

Specification

College

Reality

9-12

Spec says college; product says 9-12.

2/4 Value Hierarchy +

+Value Propaligned

Specification

One place for everything related to a piece of work, rather than decisions scattered across Slack, Notion, Jira, and email ^[5]

Reality

Organize team work into structured project spaces with integrated communication and task management ^[▣6]

Same centralization goal; spec emphasizes anti-chaos, product emphasizes structure.

+Per Pagemajor drift

Specification

Page	Primary Element	User Action
Message board	Posts with full formatting	Make announcements, decisions, and discussions that persist ^[6]
To-do lists	Named task lists	Create and manage tasks as a team ^[7]
Campfire	Project chat room	Real-time communication scoped to project team ^[8]
Schedule	Milestone dates and events	View project timeline ^[9]
Hey! menu	Centralized notifications	Check all notifications in one place ^[10]

Reality

Page	Primary Element	User Action
Home	Project list with My Project and sample projects	Navigate to existing projects
Project view	Tool tabs (Message Board, To-dos, Docs & Files)	Access project tools
Template creation	Template name input field	Name and configure project template

Spec lists tool pages; product shows navigation and templates.

+Feature Stackminor drift

Specification

Feature	Prominence	Clicks	Kano
Message board	high	?	must-have
To-do lists	high	?	must-have
Campfire group chat	high	?	must-have
Schedule	med	?	must-have
Automatic check-ins	med	?	performance
Hill Charts	med	?	delighter
Mission Control	low	?	performance
Lineup	low	?	performance

Reality

Feature	Prominence	Clicks	Kano
Projects	high	1	must-have
Message Board	high	2	must-have
To-dos	high	2	must-have
Schedule/Lineup	med	1	performance
Templates	med	2	performance
Pings	med	1	delighter
Hey!	low	1	delighter

Core features align; product adds Projects and Templates prominence.

+Color Semanticsnot in spec

Specification

—

Reality

Color	Meaning
green	primary action buttons like 'Upgrade to add another project' and 'Invite people'
gray	secondary navigation and inactive states
brown	section headers like 'SAMPLE PROJECTS' and 'YOUR SCHEDULE'

Product documents color usage; spec omits this detail.

1/4 Workflows +

+Journeysmajor drift

Specification

Journey	Steps	Success State
Six-week cycle execution	Team receives shaped work from betting table → Team defines their own tasks within project boundaries → Team makes design decisions on the fly → Team ships work within six-week deadline	Meaningful work shipped on consistent cadence ^[11]
Shape Up process	Set boundaries for the problem → Rough out elements of the solution → Address risks and rabbit holes → Write the pitch → Present to betting table → Get selected for next cycle	Shaped work committed to six-week cycle ^[12]

Reality

Journey	Steps	Success State
Create new project	Navigate to home → Click upgrade to add project → Set up project details → Configure project tools	New project appears in project list
Add tasks to project	Navigate to project → Click To-dos → Click New list → Name the list → Add individual tasks	Task list visible in project
Create project template	Navigate to templates → Click new template → Name template → Configure settings → Set up template structure	Template available for future projects

Spec shows Shape Up cycles; product shows basic project creation.

+Cog Walkthroughnot in spec

Specification

—

Reality

Step

Try

See

Link

Progress

Navigate to home

Pass

Click upgrade to add project

Friction

Pass

Friction

Pass

Button says 'Upgrade' which suggests payment rather than project creation

Navigate to project

Pass

Click To-dos

Pass

Click New list

Pass

Name the list

Pass

Friction

Form submission buttons failed to respond in testing

Navigate to templates

Friction

Pass

Templates not discoverable from main navigation, requires direct URL

Click new template

Pass

Name template

Pass

Product provides detailed walkthrough analysis; spec has none.

+Friction Mapnot in spec

Specification

—

Reality

Navigate to home	zero
Click upgrade to add project	acceptable
Navigate to project	zero
Click To-dos	zero
Click New list	zero
Name the list	guided-only
Navigate to templates	guided-only
Click new template	zero
Name template	zero

Product maps friction levels; spec has none.

0/4 Onboarding +

+First Minutenot in spec

Specification

—

Reality

User sees a demo account with sample projects showing Basecamp's structure of projects containing message boards, to-dos, and files ^[7]

Product shows demo account experience; spec omits onboarding.

+Time To Valuenot in spec

Specification

—

Reality

Explore sample projects to understand how Basecamp organizes work

Product describes sample project exploration; spec omits this.

+Time To Value Clicksnot in spec

Specification

—

Reality

Product measures clicks to value; spec omits metrics.

+Assessmentnot in spec

Specification

—

Reality

Learning through sample projects rather than guided onboarding; uses real project examples with clear tool categories

Product evaluates onboarding approach; spec lacks assessment.

4/4 Emotional Register +

+Primary Emotionaligned

Specification

Calm

Reality

Calm

+Feels Likealigned

Specification

Fewer meetings, less process overhead, and a clear cadence of meaningful shipments ^[13]

Reality

Having organized project folders where everything has its designated place and team members know where to find information ^[8]

Both emphasize organization and clarity over chaos.

+Does Not Feel Likealigned

Specification

An endless stream of micro-tasks or scattered coordination chaos ^[13]

Reality

Does not feel like a rapid-fire productivity system (Slack/Discord) — interactions are structured around projects rather than continuous streams ^[9]

Both reject scattered coordination and task streams.

Specification sources

1 Basecamp organizes work around projects — each project has its own message board, to-do lists, file storage, schedule, and group chat (Campfire). The goal is to avoid tool sprawl: one place for everything related to a piece of work
2 Teams are either scattered across too many tools (half in GitHub issues, half in Slack, decisions lost in email threads) or suffer from the opposite extreme: a heavy Scrum or Jira process that generates overhead without progress
3 Basecamp — $299/month flat, unlimited users. No per-seat pricing. This is explicitly positioned as anti-enterprise-SaaS: one price, everyone in, no negotiation
4 Software product teams at established companies — particularly those burned by Jira's complexity or the chaos of Slack + email + spreadsheet coordination
5 one place for everything related to a piece of work, rather than decisions scattered across Slack, Notion, Jira, and email
6 Message board — For announcements, decisions, and discussions that don't need to be real-time. Posts have full formatting and can be commented on
7 To-do lists — Created by the team, not assigned top-down. Tasks are grouped into named lists. Anyone can create to-dos
8 Campfire (group chat) — Per-project chat room for loose, real-time communication. Not the same as a company-wide Slack channel; scoped to the people working on the project
9 Schedule — Milestone dates and events relevant to the project, visible to the whole team
10 Hey! and Pings — The Hey! menu centralizes all notifications
11 Neither produces the feeling of 'making it' — shipping meaningful work on a consistent cadence
12 Four steps: Set boundaries → Rough out elements → Address risks and rabbit holes → Write the pitch
13 Basecamp markets itself to teams that want fewer meetings, less process overhead, and a clear cadence of meaningful shipments rather than an endless stream of micro-tasks

Reality sources

▣ 1 Homepage shows 'Lineup' navigation for project schedules and 'Your Schedule' and 'Your Assignments' sections
2 Task creation requires navigating to project, then To-dos, then New list with multiple form fields
3 Pings section shows 'You don't have any Pings yet' suggesting structured rather than instant communication
4 Lineup page shows 'Scheduled projects' focused on project timelines, not calendar appointments
5 Docs & Files appears as tab within project context, not standalone document management
▣ 6 Homepage prominently displays project list with sample projects showing Message Board, To-dos, Docs & Files structure
7 Sample projects 'Getting Started' and 'Making a Podcast' demonstrate typical Basecamp project organization
8 Clean layout with organized sections and clear project boundaries creates structured workspace feeling
9 Communication happens through Message Board and Pings rather than chat streams, with structured project contexts