Skip to main content

Use plain language so guidance is easy to understand

Make Latitude’s recommendations easier to understand at a glance, so users can quickly see what to do next.

Kenneth’s feedback

“I don’t want to have to ‘think’ too hard when using the tool. If users can quickly understand and get it, then I think they will get value quicker.”

Kenneth pointed to this headline in the Dashboard → Latitude Guidance card:

“Clarify how you judge DMs and profile views before calling LinkedIn effective.”

The wording is hard to interpret. It is also unclear whether Latitude is suggesting a post topic or asking the user to assess their LinkedIn results.

Requested improvement

  • Use familiar words and short, direct sentences.

  • Say clearly what the user should do next.

  • Make the headline, explanation, and button describe the same action.

  • Apply this to both interface copy and AI-generated guidance, while preserving the intended meaning.

Example

If the intended action is to write a post:

Recommendation: Write a post about how you tell whether LinkedIn is helping your business.

Button: Draft a post about this.

Success looks like

Users can explain the recommendation and identify their next step without additional help.

Feedback from Kenneth Fong, recorded on his behalf by Brian.

Implementation details and acceptance criteria — PROD-328

Status: Resolved4 comments

Log in to comment and vote

Comments4

  • Brian Martynowicz

    Team•

    Sep 16

    Released: clearer guidance across Latitude

    Kenneth Fong was reviewing a recommendation Latitude had generated from his LinkedIn activity.

    The idea behind it was useful: write about how you decide whether LinkedIn is helping your business. But the Dashboard headline said:

    “Clarify how you judge DMs and profile views before calling LinkedIn effective.”

    Kenneth’s response was direct:

    “I don’t want to have to think too hard when using the tool.”

    He was right. A useful insight wrapped in confusing language is not useful enough.

    We have now:

    • Rewritten Dashboard and Content Library guidance, labels, explanations, settings copy, analytics notes, and public website language in plain English.

    • Changed the recommendation engine so each suggestion explains what Latitude noticed, what to do next, and why it matters.

    • Added quality checks that reject vague, jargon-heavy, or mismatched suggestions before users see them.

    • Verified the changes with real account data across desktop and mobile.

    Kenneth’s feedback led us to improve the broader system behind one awkward sentence. Thank you, Kenneth, for pushing us to make Latitude easier to understand.

    Visit Kenneth Fong’s YouTube channel
    Watch Kenneth’s Latitude review

    This improvement is now live.

    • AppSumo Customer

      •

      Sep 16

      Thank you for quickly working on this update! ❤️

      • Brian Martynowicz

        Team•

        Sep 24

        Our pleasure.

  • Brian Martynowicz

    Team•

    Sep 15

    Development update

    This request is now in development. We expanded it beyond the Dashboard sentence to cover generated guidance, labels, tooltips, tours, Settings, empty and error states, the Chrome extension, public comparisons, and the marketing website.

    We also added a plain-language check for generated suggestions. Vague prompts such as “Share one change to your working process and what happened” are rejected and replaced with a specific topic and next action.

    The product and website changes pass local tests and visual review. Staging review and customer validation remain before release.