Skip to main content

Thomas, 29 — Employee (Developer)

Who he is​

Thomas is a full-stack developer working on three projects simultaneously. He's good at his job but terrible at keeping track of context — what he decided last week, what the client said in that one call, what the status of the PR review is. He uses Notion, Slack, JIRA, and his own scattered notes. He wastes 20 minutes every morning just remembering where he left off.

His day before Morphee​

  • Morning: Opens laptop. 47 Slack messages, 12 JIRA notifications, 3 PR reviews pending. Can't remember what he was working on Friday. Spends 20 minutes re-reading his own code to get context back.
  • Midday: In a call, client asks about a decision made 2 weeks ago. He vaguely remembers but can't find the Slack thread. Says "let me get back to you" — adds it to a mental list he'll forget.
  • Afternoon: Finishes a feature, pushes a PR. Forgets to update the JIRA ticket. Manager pings him about status.
  • Evening: Has three browser tabs with "articles to read later" and a note that says "look into Redis caching for the auth service" with no context on why.

His day with Morphee​

[Morning, 9:00]
Thomas: "Where was I?"
Morphee: "Welcome back! Friday you were:
  - Working on the payment API refactor (branch: feat/payment-v2)
  - Blocked on: waiting for Sara's review on PR #234
  - You noted: 'Need to handle the edge case where payment
    fails after inventory is reserved'

  Overnight:
  - Sara approved PR #234 with 2 minor comments
  - Client emailed about the dashboard loading time
  - Alex merged the caching PR you were waiting for

  Suggested priority:
  1. Address Sara's PR comments (10 min)
  2. Continue payment edge case
  3. Reply to client re: dashboard (I've drafted a response)"

[During a call, 11:00]
Thomas: "What did we decide about the rate limiting approach?"
Morphee: "On January 28, you discussed rate limiting with Julie and Alex.
  Decision: token bucket at the API gateway level, not per-service.
  Reason: simpler to manage, Alex offered to own it.
  Status: Alex hasn't started yet (not in current sprint)."

[After coding, 16:30]
Thomas: "I just pushed the payment edge case fix"
Morphee: "Nice! I'll:
  - Update JIRA ticket PAY-142 to 'In Review'
  - Add PR link to the ticket
  - Notify Sara for review (she reviewed the related PR)
  Want me to write the PR description from the diff?"
Thomas: "Yeah go for it"
Morphee: [Generates PR description from git diff]

Key features used​

  • Spaces: Project Alpha, Project Beta, Personal Dev, Team Space
  • Integrations: JIRA (ticket updates), GitHub/GitLab (PR status), Slack (threads), Calendar
  • Memory: Decision logs from meetings, code context, personal notes, client communication
  • Skills: Morning context resume, meeting recall, PR automation, status sync

Why it works for him​

Thomas's problem isn't productivity tools — he has too many. His problem is context fragmentation. Information lives in 5 different places and his brain is the only thing connecting them.

Morphee becomes his second brain — it remembers what he decided, what he was working on, what's waiting for him. The morning "Where was I?" question saves him 20 minutes of context recovery every single day.

Multiplied across a team: fewer "What's the status?" pings, fewer lost decisions, fewer duplicate conversations.