Skip to content
Silent Potato.
SearchTagsEN/中文
  • Start
  • Writing
  • Columns
  • Projects
  • Research
  • Work with me
  • Photos
  • About

Writing

Documents Are Not Records, but Collaboration Interfaces

A practical way to write technical documents: state the conclusion and problem clearly first, then use the right structure to carry the plan, progress, and details.

LiyukLiyukPublished October 22, 2020Updated August 14, 20265 min read
  • #Writing
  • #Technical Writing
  • #Communication
  • #Work & Leadership
  1. 1Documents Are Not Records, but Collaboration InterfacesShort · 5 min readThis chapter
  2. 2Why Technical Knowledge Bases Need Entry PagesShort · 5 min read
  3. 3Turning Spoken Ideas into Decision-Ready DocumentsShort · 3 min read
TipIf this helped

If this landed for you, consider dropping me a coffee — it keeps me writing.

Buy me a coffee →

Thanks for reading — only if you feel like it.

Share to

XWeiboTelegramWhatsAppLinkedInFacebook

WeChat

Scan with WeChat

Open this article on your phone, or forward it to a friend.

Enjoy this site?

orSubscribe via RSS
← PreviousAchievement Is Not a Reward: On Pressure, Delivery, and Self-Recognition
Next →What a Reusable Engineering Retrospective Should Leave Behind
View the column “Documentation & Knowledge”Next: Why Technical Knowledge Bases Need Entry Pages →

Keep reading

Maybe related to this one.

  • WritingTurning Spoken Ideas into Decision-Ready DocumentsDistill scattered thoughts into a document that can be discussed and acted on: tools handle the organizing, people handle the judgment.Read on →

    same column · shared 3 tags

  • WritingThemed One-on-Ones: From “Not Knowing What to Talk About” to a Topic MapSolve one problem per conversation, with each theme lasting 30 to 60 minutes. How to use this series, an overview of its topics, and the three closing principles.Read on →

    shared 2 tags

  • WritingStart by Defining the Problem: How to Open a One-on-OneWhen you don't know how to open or what to talk about, begin by defining the problem clearly. A question-and-answer checklist that managers and reports alike can follow.Read on →

    shared 2 tags

© 2018–2026 Liyuk. Built slowly, published openly.

ElsewhereGitHub ↗X ↗LinkedIn ↗Email ↗Links ↗Favorites ↗RSS ↗
CC BY-NC-SA 4.0