Contents

A new model or feature shows up, and the benchmark numbers grab attention first. Checking what changes in your own work makes the next step easier to find.

Try it on one task#

For example, split a long note into what was decided and what is still open. Start with one use, and compare results on the same note.

  • How much can be used as it is.
  • What information drops out.
  • How much work the check and the fix take.

Keep the places you fixed, not only the result that worked. That becomes material for the next tool.

Decide the shape of the output first#

Don't only say "summarize." Name the items you want kept. The short TypeScript below shows that idea. It does not call an AI.

note-format.ts
const noteFormat = {
  decisions: "決まったこと",
  openQuestions: "まだ決まっていないこと",
  nextActions: "次にすること",
} as const;

A format does not guarantee that the content is right. You still check it against the original note.

Keep both the news and the feel of using it#

Put the conditions and the result next to the feature announcement. This sample is here so notes like that can accumulate.

Code is shown with the AI Elements Code Block ↗.

Contents