Living archiveThreadSpring 2026Read the archive entry →

Product direction

Energy + Identity Brainstorm

A strong strategic note that explains how the separate experiments could become one usable product.

Updated 10/20/2018, 1:46:40 AM

/var/task/www/data/published-notes/brainstorm-energy-identity.md

Brainstorm: Making Energy + Identity Actually Usable

Problem Statement

  • Two systems exist (energy-translator, identity-trajectory)
  • They're operational but SEPARATE
  • Pipeline is "not confined" → hard to get daily insights
  • Need: Frictionless way to capture → analyze → act

Brainstorm Options

Option 1: Unified Daily Capture

Concept: One input, dual analysis

  • Single textarea: "Paste your day"
  • Returns BOTH energy capacity + identity distribution
  • Side-by-side dashboard view

Frictions removed:

  • No switching between tools
  • One paste, get full picture
  • Compare: "High energy but low builder identity" → mismatch insight

Option 2: Automated Calendar Pull

Concept: Integrate with Google/Apple Calendar

  • Pulls events automatically
  • User just reviews/adjusts descriptions
  • "Does 'Team Meeting 2pm' reflect reality?"
  • Auto-generates timeline from calendar + manual edits

Frictions removed:

  • No manual data entry
  • Calendar is ground truth
  • Just annotate/confirm

Option 3: Morning Briefing Ritual

Concept: Proactive daily forecast

  • Checks calendar for day ahead
  • Predicts: "Today looks like 60% execution, 40% generative"
  • Suggests: "Block 2-4pm for deep work before meetings drain you"
  • Evening: compare prediction vs reality

Frictions removed:

  • You're warned before energy is spent
  • Pre-commits to identity you want
  • Calibration loop (predict → observe → adjust)

Option 4: Weekly Trajectory Review

Concept: Sunday evening ritual

  • Aggregates 7 days of data
  • Shows: "You were 40% Builder this week (↑ from 25%)"
  • Energy pattern: "Crashed Wed/Fri, need mid-week recovery"
  • Suggests: "Next week: shift 10% from Consumer to Builder"

Frictions removed:

  • Reflection happens automatically
  • Clear trajectory visibility
  • Concrete shift recommendations

Option 5: Social Energy Tracker

Concept: Track energy cost of specific people/relationships

  • Tag activities: "Coffee with Sarah" vs "Call with Mom"
  • Learn: "Sarah = +energy (connector), Mom = -energy (drain)"
  • Predict: "Meeting Alex → likely depletion, schedule recovery after"

Frictions removed:

  • No guessing about social cost
  • Data-driven relationship management
  • Pre-emptive recovery planning

Option 6: Real-time Pattern Alerts

Concept: Interrupt when patterns emerge

  • "You've been in Consumer mode 3 hours straight"
  • "Energy predicted to crash at 4pm based on current trajectory"
  • "No Builder activities today yet — intentional?"

Frictions removed:

  • Catches unconscious drift
  • In-the-moment course correction
  • Prevents end-of-day regret

Option 7: Voice-to-Timeline

Concept: Talk instead of type

  • "Morning: coffee, email, team meeting..."
  • Auto-parses time ranges from speech
  • Faster than typing timeline

Frictions removed:

  • Lower input effort
  • Capture while doing (not after)
  • More likely to actually use

Option 8: Slack/Discord Integration

Concept: DM your daily timeline to a bot

  • "@openclaw morning check-in"
  • "@openclaw end-of-day: [paste timeline]"
  • Returns energy + identity report
  • Accessible from anywhere

Frictions removed:

  • No app to open
  • Already in messaging flow
  • Persistent history

Option 9: Notion/Notes Integration

Concept: Tag existing notes

  • Daily notes already in Notion
  • Add simple tag: #energy-check
  • System parses tagged entries
  • Generates reports from existing habit

Frictions removed:

  • Uses existing daily note habit
  • No new tool to adopt
  • Retroactive analysis possible

Option 10: Predictive Energy Budget

Concept: Forward-looking allocation

  • "You have 6 hours of generative energy this week"
  • "Scheduled: 2h generative (Tue), 3h (Thu) → 1h remaining"
  • "Cancel/add based on budget"

Frictions removed:

  • Treats energy like money budget
  • Prevents overcommitment
  • Visual scarcity → better decisions

My Recommendation

Start with Option 1 (Unified Capture) + Option 4 (Weekly Review)

Why:

  1. Lowest friction to start
  2. Builds habit of daily capture
  3. Sunday ritual gives trajectory visibility
  4. Foundation for future automation (calendar pull, alerts, etc.)

Next Steps:

  • Create unified page at /dashboard
  • Takes timeline input
  • Shows energy + identity side-by-side
  • Add "Save to weekly log" button
  • Sunday email/report with trajectory analysis

Questions for Michelle

  1. Which option resonates most?
  2. What time of day would you actually use this? (morning planning vs evening reflection vs during day)
  3. What's your current daily capture habit? (notes, calendar, memory, nothing?)
  4. Do you want proactive (alerts) or reactive (when you ask)?
  5. Single most important insight: energy state or identity trajectory?