DEV Community

Cover image for A Checklist I Run in a TikTok Viewer Before I Paste Notes Into a Ticket
Jenny Wei
Jenny Wei

Posted on AI-assisted

A Checklist I Run in a TikTok Viewer Before I Paste Notes Into a Ticket

When a ticket lands on my desk with a repo link, a stack trace, and a failing test, I know what to do. Every so often I get a different kind of ticket: a public TikTok username and a request to write down what’s actually on the account. I used to open the official app, scroll, and paste half-formed notes into the ticket. Those notes were hard for the next person to reuse. I now keep a short checklist and run it in a tiktok viewer, in a browser, so the write-up looks like something an engineer or a PM can pick up without asking me what I meant.

This article was created with the help of AI.

What’s in the ticket, and what isn’t

The ticket is usually thinner than people think. It has a username. It might have a product question, like whether a creator is posting original clips or mostly resharing other people’s work. It does not include permission to treat the account as a private investigation, and it does not ask me to produce engagement math I cannot stand behind.

I only open a public profile the team has already named. If the username in the ticket is vague, I stop and ask. I do not go looking for people who did not show up in the work.

What I ask the TikTok viewer to show me

I only need the public page, in a form I can move through in a fixed order: Posts, Reposts, Followers, and Following, plus the comment threads under the videos. I don’t need a strategy from the page. I need a view I can check off, one item at a time.

The checklist I actually run

I keep this in a note I paste at the top of a scratch file. I don’t skip around. If I skip around, I start writing conclusions before I’ve looked at the work.

1. Confirm the profile and stay in the browser

I check the username twice. Then I stay in a browser window that’s separate from my personal apps. I don’t want research mixed into a feed I use after work, and I don’t want to sign into TikTok on a machine I share with other tasks.

2. Split posts from reposts before writing a sentence

This is the step I used to get wrong when I scrolled a phone. A reshared clip can look like the creator’s own work if you’re moving too fast. I look at Posts first and only then at Reposts. If I need a line in the ticket about “what they publish,” it has to come from Posts. If I need a line about “what they pass along,” it comes from Reposts, and I label it that way.

When I’m ready to look, I open the public profile in a tiktok viewer, enter the username, and wait for the public page to load. No TikTok login. The page groups the account into Posts, Reposts, Followers, and Following, which is the same split I already use in the checklist.

3. Read a few comment threads, not a dashboard

I pick a small set of videos, usually recent posts, and I read the comments. I’m not counting them and I’m not inventing a performance story. I’m listening for the questions people actually ask, the jokes that keep showing up, and anything that would change how I’d describe the content to a teammate.

The comments live under the videos, and I can read them in the same pass. If a thread includes a personal detail I would not want forwarded in a ticket, I rewrite it as a general observation, or I leave it out.

4. Treat followers and following as context, then stop

Followers and Following are public lists. They’re easy to over-read. Those lists are on the same public page I already have open in the tiktok viewer, so I don’t bounce back to the official site just to peek at them. I note rough scale and, at most, a few obvious public accounts that help explain the neighborhood this profile sits in. I do not turn the lists into a character study, and I do not copy a pile of names into a ticket that might get forwarded.

5. Save a file only if the ticket needs a still

Sometimes the ticket needs a still for a slide or a design review. In that case I download one public video and grab a frame. I keep the file in a folder named with the date and the ticket id, and I delete it when the work is over. I don’t re-upload anyone’s video. If someone else on the team needs to see the clip, I point them to the original post.

A blank notebook beside a keyboard on a desk, with a second monitor turned away so the screen is not readable

This image was created using an AI image creation program.

The note template I paste into the ticket

I use the same headings every time. It’s boring, and that’s the point. The next person shouldn’t have to decode my shorthand.

# TikTok research notes
- Ticket:
- Username (public, already named in the ticket):
- Date checked:

## Posts
- What they publish themselves:
- Examples I actually watched:

## Reposts
- What they pass along:
- Anything I almost mislabeled as theirs:

## Comments
- Tone I heard:
- Questions people were already asking:
- Anything I left out because it didn’t belong in a shared ticket:

## Followers / Following
- Rough public context only:
- I stopped at:

## Files
- Local reference file (delete after the work):
- Original post URL to share instead of the file:
Enter fullscreen mode Exit fullscreen mode

If a section has nothing useful, I write “none” and move on. An empty heading is better than a sentence I invented to make the notes look complete.

What I refuse to put in the ticket

I don’t screenshot a comment that includes someone’s display name plus a personal detail. Public is not the same as fair game for a shared doc.

I don’t use this process to lurk on people who didn’t ask to be researched. If the work expands to a second account, that account has to be named in the ticket too.

I don’t paste download links as if they replace the original URL. A saved file is a temporary reference, not a source of record. The ticket should point at the original post, not at the tiktok viewer I happened to use to look at the account.

And I don’t write as if I measured growth, reach, or “what works.” I only write what I can point back to on the public page: the posts, the reposts, a few comment threads, and light context from the public lists.

Next time a ticket shows up with only a username, I won’t start by scrolling the official app and hoping I remember what I saw. I’ll run the checklist, fill the template, and hand the ticket back in a shape someone else can use. If I need to look at the public page again, I’ll open the same tiktok viewer in the browser and start at Posts, not at whatever the feed wants to show me.

Disclosure: I have a business connection to the site linked in this article.

Top comments (0)