Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Insight: Spread the love #2224

Open
4 of 20 tasks
smoreface opened this issue Feb 26, 2015 · 0 comments
Open
4 of 20 tasks

New Insight: Spread the love #2224

smoreface opened this issue Feb 26, 2015 · 0 comments

Comments

@smoreface
Copy link

One-liner

  • How many and which people you replied to on Twitter in the last week.

Describe what this insight is in a single sentence. This is the description that appears in ThinkUp's insights list, so phrase it like the others are. Current insights single sentences are:

  • Post activity spikes for the past 7, 30, and 365 days.
  • How often you referred to yourself ("I", "me", "myself", "my") in the past week.
  • How many more users a message has reached due to your reshare or retweet.

Insight preview
Insight preview

Full explainer

How does it make the user feel? What is the goal of this insight?

  • Reminds them that it feels good to talk to other people online (especially if the conversations had or people were cool). Reminds them of conversations that they've had that they might've forgotten.

Audience for the insight

Which networks, if any, are excluded from this insight?

  • Facebook, though it could probably work there too.

Does this insight serve users with less or more activity?

  • More activity
    First-run: does this insight show up on a user's first crawl?
  • Maybe?

    How often this insight runs

  • Always (triggered by a data event, check the data and update insight on every crawl)
  • Daily (check the data once a day, don't regenerate every crawl)
  • [√ ] Weekly on a fixed day (specify day of week per network to space these out)
  • Monthly on a fixed day with bonus magic day within first 2 weeks of use (specify day of month per network to space these out)
  • Annual on a fixed date (specify day of year)
  • Annual every 365 days from first appearance

Headline

You spread the love

Include multiple variations, use third person and variables for localized network terminology.

For example:

  • %username has passed %total %followers!
  • More than %total people are %following %username

Body

You had conversations with three people on Twitter this week!

Include multiple variations whenever possible.

For example:

  • That's more than the population of Belize.
  • That's more people than can fit in Yankee Stadium.

Tout

  • Be reminded of great people that you've met online.

Explain how ThinkUp can help potential users, basing copy on the insight.

For example:

  • Want a handy list of the links you've favorited? We can help!
  • Get a look back at what you were doing on this day in years past.

Criteria and logic

Describe the rules for when this insight runs.

  • What data does this insight need? Last week's posts? Last month's? Just the user's posts?
  • Does the insight count replies as well as non-replies?
  • Are there baseline comparisons? What is the logic around the comparison?
  • Are there special copy cases? (for example, if the baseline comparison matches)
  • Is there a minimum threshold for any bit of data before the insight should get generated?

Emphasis

  • High
  • Medium
  • Low

Included elements

  • Headline
  • Text
  • Header image (image off to the left in side-by-side style insights: https://c1.staticflickr.com/5/4042/4439563089_d7ecec12f2_z.jpg?zz=1)
  • Hero image (giant image on top)
  • List of user(s)
  • List of post(s)
  • List of link(s)
  • Action button (please specify button label and URL button should link to)
  • Line chart
  • Bar chart
  • Other viz
  • Other graphic treatment

Action button

Specify the following action button attributes:

Hero image

If your insight includes a hero image, we encourage you to use public domain or CC-licensed images. Hero images should be at least 540px wide and be landscape. (They can be portrait, but then they're quite tall.)

Specify the following hero image attributes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant