> ## Documentation Index
> Fetch the complete documentation index at: https://protocol.tome.gg/llms.txt
> Use this file to discover all available pages before exploring further.

# Basic Growth Journal

> The simplest way to accelerate your learning through structured reflection

The Growth Journal is the foundation of all Tome.gg protocols — a simple, systematic approach to tracking your learning that creates compound growth over time.

## The Minimal Version

### Daily Entry (2-3 sentences)

```
## [Date] - What I Learned Today
- [Write 2-3 sentences about what you learned]
```

### Weekly Challenge

```
## This Week's Challenge
- Problem: [What challenge did you face?]
- Approach: [How did you try to solve it?]
- Outcome: [What happened?]
```

### Monthly Share

```
## Monthly Insight
- [One thing you learned that's worth sharing publicly]
```

## Getting Started

<Steps>
  <Step title="Choose Your Tool">
    Use any document editor:

    * [Google Docs](https://docs.new)
    * [Notion](https://notion.so)
    * Markdown file
    * Even a simple text file
  </Step>

  <Step title="Start Small">
    What did you learn today? Write just 2-3 sentences. Don't overthink it.
  </Step>

  <Step title="Build the Habit">
    Do this daily for one week. Consistency matters more than length, correctness,
    completeness, or precision.
  </Step>

  <Step title="Add Structure">
    After a week, add weekly challenges and monthly insights.
  </Step>
</Steps>

<Info>
  **Remember**: The best growth journal is the one you actually use. Start
  simple and build from there.
</Info>

## Example Entry

```markdown theme={null}
## March 15, 2024 - What I Learned Today

- Learned about React's useCallback hook and how it prevents unnecessary re-renders
- Discovered that it's only useful when passing callbacks to optimized child components
- Realized I was overusing it in my previous projects without understanding the performance implications

## This Week's Challenge

- Problem: My React app was re-rendering too often causing performance issues
- Approach: Used React DevTools Profiler to identify components that render unnecessarily
- Outcome: Found 3 components that were re-rendering due to object creation in render, fixed with useMemo

## Monthly Insight

The key to React performance isn't using every optimization hook available—it's understanding when and why to use them. Measure first, optimize second.
```

## Success Metrics

* ✅ **Day 7**: You've written for a full week
* ✅ **Day 30**: You've built a sustainable habit
* ✅ **Day 90**: You can see patterns in your learning

## Advanced Options

Once you've established the habit:

<CardGroup cols={2}>
  <Card title="Collaborative Growth Journal" href="/formats/growth-journal">
    Learn about collaborative editing with mentors and peers
  </Card>

  <Card title="Training Definition" href="/training/definition">
    Learn the motions of productive and unproductive cycles in training
  </Card>
</CardGroup>