Matt Lane · Notes← All notes
2024-12-24 · Writing & craft

Packaging

Effective document creation requires a thoughtful approach that goes beyond traditional writing techniques. Doing this well can create compelling documents that effectively communicate complex ideas. Always prioritize clear communication over digital convenience and form. And remember, as the reader, always evaluate the content, the concept, not the pitch.

The worst medium for writing and reading has got to be the slide deck/slideshow presentation format. It’s constrained linearity. Worst symptoms: random fragmentation, contextless abstraction, dominance of form over content.

Syntactically link words (and visuals) into a narrative.

The goal of packaging shaped work is to provide clear guidelines while allowing room for adaptation and creativity.

Directly integrate images, charts, and diagrams into the narrative.

Presenting information in an adjacent rather than sequential order.

Enable readers to compare multiple data values and see relationships.

Discuss a large concept in segments while illustrating how parts fit into the whole. This applies to words and visuals.

More on this here:

Software Feature Package (Design Doc) Examples:

[https://basecamp.com/assets/images/books/shapeup/1.5/to-do_groups_pitch.png](https://basecamp.com/assets/images/books/shapeup/1.5/to-do_groups_pitch.png)

[https://basecamp.com/assets/images/books/shapeup/1.5/group_notifications_pitch.png](https://basecamp.com/assets/images/books/shapeup/1.5/group_notifications_pitch.png)

[https://public.3.basecamp.com/p/o2BC3gFt7Sj6fodjtDi7WJrY](https://public.3.basecamp.com/p/o2BC3gFt7Sj6fodjtDi7WJrY)

You can easily use something like Google Docs or Docs in Miro to package shaped work.

Discussion

**Packaging Shaped Ideas (delegation of real work)**

**Key Idea:** Present ideas in a cohesive, narrative-friendly way—avoid the linear constraints of traditional slide decks. Break the concept into meaningful “chunks,” integrate text and visuals contextually, and guide the reader through a smooth story.

- **Decomposition:**

- Involves **chunking** the bigger concept or solution into smaller, distinct sections (fewer than 10) with *clear, memorable names.*
- Each chunk addresses a specific part of the overall idea that was shaped—user flows, design constraints, business outcomes, etc.
- **Abstraction:**

- Stays *conceptual* by naming each section according to its core purpose rather than listing every minor detail.
- Maintains a higher-level narrative that can be fleshed out with specific illustrations or examples when needed.
- **Pattern Recognition:**

- By chunking and naming, you may notice **recurring themes** across sections—e.g., repeated user pains, repeated design patterns, or overlapping constraints.
- The approach of weaving text + visuals helps identify which ideas connect or reappear in multiple parts of the design.
- **Algorithm/Procedure:**

- Follows a **structured workflow**:

1. Identify the main chunks (the “top-level” sections).
2. Give each chunk a meaningful, action-oriented name.
3. Write a **flowing narrative**, embedding images near the relevant text.
4. Conclude with a synthesis or overview that ties the chunks together.
- This ensures the final document (or “package”) is coherent, easy to reference, and useful for handoff.