ナビゲーションにスキップ

How do I continue Reddit user research after changing tools, with evidence for each finding?

To continue Reddit user research after switching tools, keep the old tool’s exports, community list, search terms and review labels, and resume from the question the old research left unanswered. Find candidate posts in community feeds, or read comments directly when you have a post link. Add the new quotes and follow-up questions to your existing worksheet.

For example, in note-sync research, list which devices or steps the saved examples do not cover yet, then read discussions about the missing devices or steps. Keep the old labels and review the new evidence with the same criteria.

Keep your existing research

Save the exports, community lists, search terms, topic definitions and manual notes from the old tool. Keep the old labels and findings next to the new material so you can compare old and new findings.

For GummySearch account access and export options, read GummySearch’s official notice and check the options in your account. This page covers the next research round; importing an old workspace depends on the workspace’s actual export format and is a separate task.

Start with a question you can investigate

Write the question so that discussions can answer the question, for example: “Under what conditions do users experience note-sync difficulties, and what explanations appear in the discussions?”

  1. Choose two communities you have confirmed are relevant. Record why each community fits, and retrieve one NEW feed page per community with data:reddit.app.fetch_subreddit_feed. If you already have target threads, skip discovery.
  2. Select up to three relevant discussions. Review each title and the post content, and record a reason such as “describes a sync conflict after working offline.”
  3. Read the comments of each selected discussion. Retrieve one page per selected thread with data:reddit.app.fetch_post_comments, keeping parent and reply context. Use the comments to decide what still needs investigation.
  4. Create research entries. Record source excerpt, theme, conditions, interpretation and verification needed as separate fields. Then decide whether each entry leads to documentation, further research or product investigation.

Each response determines its own page size. The workflow on this page discovers posts through the NEW feeds of communities you name. Keyword search across Reddit, a community’s top posts of the year and trending terms are separate tasks.

What files support each step?

StepWorkflowDeliverable
Select discussionsCommunity shortlistposts.csv, source/coverage records and selected-comment-requests.json, with selection reasons
Read commentsComment exportPer-page CSV and original responses for text and parent/reply review
Organize observationsMerge steps in the comment guidecomments.csv, observations.csv, coverage.json, retaining unique comments and repeated observations separately
Review and deliverExcerpt-review steps in the same guidereview-labels.json, question-backlog.json, with traceable themes, excerpts and review state

Prepare each input file with the linked guide, then run the four local commands below in order:

python3 prepare_reddit_threads.py feed-inputs.json feed-review
python3 export_comments.py reddit-query-1/reddit-comments.json reddit-comments-page-1.csv
python3 merge_pages.py pages.json merged-comments
python3 reddit_review.py merged-comments/comments.csv raw-pages.json review-labels.json question-backlog.json

The four commands process saved files and do not call the API. After prepare_reddit_threads.py writes the selected-thread requests, send the selected-thread requests within your budget and save each comment response before you run export_comments.py. In raw-pages.json, set each csv_file to the same value as source_csv in the merged table so reddit_review.py can find the original response.

Write useful product findings

MaterialResearch entryNext action
A user asks which sync setting to chooseSetup question with wording and device conditionsCheck whether existing instructions are clear
A commenter reports a conflict after offline useReported experience with contextVerify version and reproduction conditions
A reply suggests another operation fixes the problemCandidate explanation with the parent commentTest or verify the explanation before documenting the fix
Someone praises effortless syncingPositive experience in a stated contextInvestigate the conditions behind the positive experience

Check each excerpt against the original comment before you summarize the excerpt. For each theme, report the number of supporting comments and of distinct threads. Count a comment once even when the comment appears in several saved observations. Theme counts describe comments, not independent customers or population shares.

Give an assistant this instruction:

Organize sync-related questions, positive experiences and proposed workarounds from the selected discussions. Keep an actual excerpt, thread link and context for each finding, with verification needed. Deliver themes and next actions without treating every reported experience as an established defect.

Keep the generated question-backlog.json unchanged, and fill proposed_action and verification_needed in a separate action copy. Keep the unreviewed and excluded counts so colleagues can continue the review.

Choose the scope and cost

This round makes at most five data requests: one feed page for each of two communities, plus one comment page for each of up to three threads. Estimate the cost with current pricing. Reuse saved threads, comments and older research instead of requesting the same material again. Additional pages, reply branches and model analysis have their own scope and cost.

The round is complete when you deliver sources, original material, themes and action items. For recurring runs, set up scheduling and state storage separately; the file workflow does not migrate the old workspace or install alerts.

Community selection · Comments and evidence review