<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Aparna Darlington</title>
    <description>The latest articles on DEV Community by Aparna Darlington (@aparnadarlington).</description>
    <link>https://dev.to/aparnadarlington</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4250375%2Fab4f7912-6ff7-425b-b806-05aeaf701a55.jpg</url>
      <title>DEV Community: Aparna Darlington</title>
      <link>https://dev.to/aparnadarlington</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aparnadarlington"/>
    <language>en</language>
    <item>
      <title>Give every interview claim a place in your notes</title>
      <dc:creator>Aparna Darlington</dc:creator>
      <pubDate>Tue, 17 Nov 2026 17:56:25 +0000</pubDate>
      <link>https://dev.to/aparnadarlington/give-every-interview-claim-a-place-in-your-notes-4eod</link>
      <guid>https://dev.to/aparnadarlington/give-every-interview-claim-a-place-in-your-notes-4eod</guid>
      <description>&lt;p&gt;A business interview can leave me with three versions of the same afternoon: the story an owner tells, the sequence I saw, and the dates in a notebook. None is automatically wrong. They answer different questions. The trouble starts when I merge them while writing and forget which detail came from where.&lt;/p&gt;

&lt;p&gt;For small-business reporting, a plain digital ledger helps me keep those differences visible. It is not a scoring system for whether somebody sounds convincing. It is a way to leave a trail from a sentence in a draft back to something I can check.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgpoityp3wi4fwbz1nks8.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgpoityp3wi4fwbz1nks8.jpg" alt="A reporter records a bookbinder’s workshop demonstration" width="800" height="534"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with a claim, not a transcript
&lt;/h2&gt;

&lt;p&gt;I give each useful claim its own row. Beside it, I record who said it, when we spoke, and where the supporting material lives. That material might be an interview time stamp, a photograph of a demonstration, or a dated notice supplied by the business.&lt;/p&gt;

&lt;p&gt;A separate column says what kind of evidence I have. “The owner remembers moving in spring” is different from “the lease began in March.” Those may eventually fit together, but they should not become the same fact just because a spreadsheet puts them next to each other.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep an observation column
&lt;/h2&gt;

&lt;p&gt;Suppose a bookbinder shows me a repair that takes several stages. I can describe the stage I watched. I cannot turn ten minutes at the bench into a confident statement about an entire week's output.&lt;/p&gt;

&lt;p&gt;My observation column keeps that boundary close to the note. I write what happened in front of me, then list the follow-up needed to understand the wider process. A demonstration can suggest a question without settling it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F37uvk9ax03wbzownhbot.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F37uvk9ax03wbzownhbot.jpg" alt="An editor compares interview notes in a structured ledger" width="800" height="534"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Make uncertainty searchable
&lt;/h2&gt;

&lt;p&gt;A long notes document hides unfinished work remarkably well. A ledger lets me filter for it. I use a small set of labels: checked, needs another source, awaiting clarification, and omit for now.&lt;/p&gt;

&lt;p&gt;The labels describe my reporting work, not the character of the interviewee. If I cannot establish a date before publication, leaving it out may be the cleanest choice. A blank in a reporting ledger is often more useful than a guess that looks complete.&lt;/p&gt;

&lt;h2&gt;
  
  
  Link records without spreading private files
&lt;/h2&gt;

&lt;p&gt;The spreadsheet does not need to contain every recording or document. A short reference to a sensibly named file is enough. I keep sensitive material in a restricted folder and share only what an editor actually needs to review.&lt;/p&gt;

&lt;p&gt;Simple software can also flag an empty evidence field or list unresolved rows before a deadline. That is a useful kind of automation: it reminds me to ask a question instead of offering an answer of its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the ledger after publication
&lt;/h2&gt;

&lt;p&gt;For a newsletter edition, I save the version used at publication and note later corrections separately. Quietly overwriting the old row makes the history harder to follow.&lt;/p&gt;

&lt;p&gt;The result is not a more complicated interview. It is a calmer editing session. When a sentence sounds too certain, I can find its source, adjust its wording, and return to the business with a precise question rather than asking somebody to tell the whole story again.&lt;/p&gt;

</description>
      <category>documentation</category>
      <category>productivity</category>
      <category>writing</category>
    </item>
  </channel>
</rss>
