Skip to main content

Work Journal App: A Reflection on Tracking Non-Revenue Generating Productivity

Problem Statement​

Tracking work is painful, yet critically important. On any time horizon—daily, weekly, monthly, or quarterly—stakeholders need visibility into how time is allocated. This serves two purposes:

  1. Self-awareness: Understanding where you dedicate your time
  2. External accountability: Demonstrating value to managers and justifying the hiring decision

The Challenge of Non-Revenue Roles​

Sales roles have clear ROI metrics. For everyone else—particularly go-to-market engineers and heads of ecosystem—the value proposition is indirect:

  • Writing blog posts doesn't directly generate revenue
  • Community building creates conditions for future revenue
  • These activities engineer realities where success becomes more likely

In a competitive job market, recognition for work done is essential for both job security and career advancement.

Solution Concept: Desktop Work Journal​

Core Principles​

Desktop-First Philosophy

  • Focus on desktop to maintain work-personal separation
  • Phones are distraction vectors (social media, YouTube, music)
  • Professional work deserves professional tools

Product Vision​

Always-On Desktop Widget

  • Persistent presence on desktop
  • One-click capture of current work state
  • Auto-categorization by areas of responsibility
  • Manual override for categorization when needed

Rich Context Capture

  • Screenshots as primary documentation ("an image speaks a thousand words")
  • Optional text annotations (or voice via something like Wispr Flow)
  • Continuous context building throughout the workday
  • Easy report generation for any time period

Implementation Strategy​

Phase 1: Manual Prototype​

Before building automated tooling, validate the concept manually:

  1. Manual screenshots captured every 10-15 minutes
  2. Notion-based cataloging of work moments, maybe in one giant Notion database with tag columns
  3. Annotations explaining context and reasoning
  4. Daily summaries of accomplishments and next-day planning

Phase 2: Automation Assessment​

Evaluate whether building a tool provides sufficient ROI:

  • Time savings vs. development effort
  • Improved consistency in documentation
  • Enhanced reflection and work improvement

Value Proposition​

Personal Benefits​

Memory Augmentation

  • Reduces reliance on memory
  • Creates searchable work history
  • Enables pattern recognition in work habits

Continuous Improvement

  • Regular reflection on work methods
  • Balanced attention across areas of responsibility
  • Weekly progress tracking across all categories

Professional Benefits​

Auditable Decision-Making

  • Documents thought processes in real-time
  • Provides context for decisions that may be second-guessed
  • Creates defensible record of strategic thinking

Entrepreneurial Documentation

  • Captures the experience of being an early employee at a disruptive startup
  • Records non-obvious decisions and their rationale
  • Builds institutional knowledge

Key Differentiators​

This isn't just work tracking—it's a work journal that:

  1. Documents the state of mind, not just the state of work
  2. Captures desktop context alongside mental context
  3. Enables retrospective analysis of decision-making
  4. Supports continuous improvement, not just documentation

Integration Considerations​

  • Relationship with external project trackers (TBD)
  • Personal detail layer vs. team-visible reporting
  • Privacy and security implications

Next Steps​

  1. Begin manual prototype for personal use
  2. Document insights and pain points
  3. Evaluate automation opportunities
  4. Consider broader applicability beyond personal use

Note: This concept emerges from the recognition that ecosystem and go-to-market roles require different success metrics than revenue-generating positions. The goal is to create a tool that makes the invisible work visible, auditable, and improvable.