Vistaly

Vistaly

Software Development

Charlottesville , VA 476 followers

Visualize and discover better product solutions

About us

Vistaly is an operating system for Outcome-oriented Product teams. - model how the business grows - identify Outcomes that will have the biggest impact on growing the business - create OSTs and learn which Opportunities will help you hit your Outcomes

Industry
Software Development
Company size
2-10 employees
Headquarters
Charlottesville , VA
Type
Privately Held
Founded
2021

Locations

Employees at Vistaly

Updates

  • Vistaly reposted this

    View profile for Maja Voje, graphic

    Best-selling Author of GTM Strategist | Advisor (helped 750+ companies inc. Fortune 500 companies to go to market) 🧭

    I can tell you everything I know about LinkedIn algo and content strategy, but you will still not do it. And you are right not to. Why? Because the right question to ask is not "What to post?" but "Should you be posting in the first place? You can use LinkedIn as a channel in ALL 7 Go-to-Market Motions. Here are some of my favorite examples: 1. 𝐅𝐨𝐮𝐧𝐝𝐞𝐫-𝐥𝐞𝐝 𝐠𝐫𝐨𝐰𝐭𝐡 (inbound, events, ...) MVP = Adam Robinson. They got RB2B to $ 1 million ARR in 12 weeks. 2. 𝐄𝐆𝐂 (𝐄𝐦𝐩𝐥𝐨𝐲𝐞𝐞-𝐆𝐞𝐧𝐞𝐫𝐚𝐭𝐞𝐝 𝐂𝐨𝐧𝐭𝐞𝐧𝐭) as Clay team does - see Patrick Spychalski, Bruno Estrella, Alex Lindahl, and others 3. 𝐕𝐚𝐥𝐮𝐞 𝐂𝐨𝐦𝐦𝐞𝐧𝐭𝐢𝐧𝐠 𝐖𝐢𝐳  strategy to penetrate other communities and get attention to your profile/content - Mac Reddin 🦕 does this beautifully. 4. 𝐑𝐞𝐩𝐮𝐫𝐩𝐨𝐬𝐢𝐧𝐠 𝐆𝐫𝐨𝐰𝐭𝐡 𝐌𝐚𝐜𝐡𝐢𝐧𝐞 can create millions of impressions and fast spikes in following. I admire Rubén D.'s work in this field. 5. 𝐎𝐮𝐭𝐛𝐨𝐮𝐧𝐝 𝐍𝐢𝐧𝐣𝐚 - lately, I have been very impressed with Arnaud Renoux work on sales triggers and prospecting on LinkedIn to get leads. And there are so many more awesome B2B examples. Which one would you add? Bottom line- they all work. I am working on a visual to illustrate how LinkedIn can be used to support various GTM Motions. v01 is presented here (draft) 📌 More info & practical examples: https://lnkd.in/dUdtRfDD Make sure you sign up. This one is a value bomb.

  • Vistaly reposted this

    View profile for Dr. Else van der Berg, graphic

    Product Management | Discovery & validation enthusiast

    One minute you're happily adding opportunities to your Opportunity Solution Tree, the next you're thinking "𝘐'𝘷𝘦 𝘤𝘳𝘦𝘢𝘵𝘦𝘥 𝘢 𝘮𝘰𝘯𝘴𝘵𝘦𝘳...." My OSTs tend to get 𝘸𝘢𝘺 too broad and unruly at first. I add every opportunity that comes up during an interview to my tree (even if it was mentioned only once), so I can start counting insights. I remove the ones that don't make 'the cut' and add structure later. Vistaly is my tool of choice to maintain my OST: I can attach insights to opportunity cards, and easily filter for the opportunity branches that are most promising with custom card settings (𝘴𝘩𝘰𝘸𝘯 𝘰𝘯 𝘵𝘩𝘦 𝘴𝘤𝘳𝘦𝘦𝘯𝘴𝘩𝘰𝘵!) But best of all is having a direct line to Matthew O'Connell, who patiently listens to my "I want to do x....can you help?" time and time again. 𝗠𝗮𝘁𝘁 𝘄𝗿𝗼𝘁𝗲 𝗮 𝗴𝗿𝗲𝗮𝘁 𝗮𝗿𝘁𝗶𝗰𝗹𝗲 𝗼𝗻 𝗵𝗼𝘄 𝗜 𝗯𝘂𝗶𝗹𝗱 𝗺𝘆 𝗢𝗦𝗧𝘀 𝗮𝗻𝗱 𝘁𝗿𝗶𝗺 𝘁𝗵𝗲𝗺 𝗯𝗮𝗰𝗸 𝗶𝗻𝘁𝗼 𝗮𝗻 𝗮𝗰𝗰𝗲𝗽𝘁𝗮𝗯𝗹𝗲 𝗳𝗼𝗿𝗺 𝗮𝗳𝘁𝗲𝗿 𝘁𝗵𝗶𝗻𝗴𝘀 𝗵𝗮𝘃𝗲 𝗴𝗼𝘁𝘁𝗲𝗻 𝗼𝘂𝘁 𝗼𝗳 𝗰𝗼𝗻𝘁𝗿𝗼𝗹...🌳 ✂️ (𝗹𝗶𝗻𝗸 𝗶𝗻 𝗰𝗼𝗺𝗺𝗲𝗻𝘁) 𝗪𝗲 𝘁𝗮𝗹𝗸𝗲𝗱 𝗮𝗯𝗼𝘂𝘁: 🔷 Homing in on ONE product outcome and ONE ICP 🔷 How to identify the right product outcome (Learning goals -> Performance goals!) 🔷 Ignoring everything that didn't come from your #1 ICP. 🔷 What I call "broad scope" ('how can we create a significantly better product') and "narrow scope" (e.g. 'how can we optimize out onboarding journey) discovery 🔷 A step by step walkthrough the workshop I ran to prune our unruly tree

    • No alternative text description for this image
  • View organization page for Vistaly, graphic

    476 followers

    👀 could be the move

    View profile for Steve Klein, graphic

    Vistaly co-founder & product nerd | ex-LaunchNotes, Atlassian, StatusPage co-founder (YC S13)

    I've talked to about 100 Product managers/leaders who are trying to "get their team more Outcomes-focused" and "do continuous discovery". Here's the biggest barrier holding most of these companies back... They don't have a clearly defined _Product Outcome_ to start with. Doing Continuous Discovery and using Opportunity-solution trees (OSTs) are where most teams start their journey to becoming Outcomes-focused. Unfortunately, many teams try to use OSTs with an unspecific, lagging _Business Outcome_ like "Increase MRR" or "Get to PMF" as the Outcome at the top of their OST. This is a recipe for disappointment. You have to break those "Business Outcomes" down into Product Outcomes, or the change in user _behavior_ you want to drive, if you're want to have success with OSTs. But this process can be confusing and difficult! I'm doing a live event with Ant Murphy (one of the fastest growing voices in Product) as we walk step-by-step through a few methods of breaking down Business Outcomes into Product Outcomes. It's July 24 at 6pm ET (which is 8AM AEST the following day in Sydney 🤷🏻♂️) - register here to join us / get the recording: https://lnkd.in/eyCQ9Aaw

    • Ant Murphy and Steve Klein event post. The event is July 24 at 6PM ET.

Similar pages

Browse jobs