But every great product team asks these two questions that Steve Jobs did at Apple.
1.What incredible benefits can we give to the customer?
2.Where can we take the customer?
Product-culture is a system of product management that is focused on addressing two questions. It’s a process of discovery and conversation with the market.
Here is six-pack of product-culture way of doing things. Some are easier to iterate others are harder to iterate aspects.
UX-Metrics-Target Persona are the most visible part of the product. Tons of experimentation, discovery and iteration happens on these aspects of product.
The North Star guiding these iterations is “Where can we take the customer?”
i.e.
A. Who is this target customer?
B. What transformation are we trying to bring to this customer? (The true metric of Customer success)
Target customer for Salesforce is/was the sales team. By building a holistic view inside a CRM, sales team are transformed from running a transaction based sales to a longer term relationship based business.
What is the product?
What job is it trying to get done?
Who is this product for?
Who would pay for it? Are the questions that get addressed by UX-Metrics-Persona.
The Why-Team-Timing are the hard to iterate aspects of product management. They are “invisible” in ways that you don’t get to observe it in a product or a blog. It’s embedded in the culture of the team. They are the behind the scenes of the product.
Why this kind of customer?
Why is now a good time to transform this customer?
How do we build and ship this product?
When do we ship this product & features?
How much would this customer value $$$ our product ? Are the kind of questions that get addressed by Why-Team-Timing.
The North Star guiding these iterations is “How big of an impact your product has on your customer?”
i.e.
A. Your customer is able to make a dent in the universe.
B. Your product is getting adopted and your product is valued in terms of $
When we ship a product, we ship our culture too. A culture is what gets built around the product while discovering the answers to the questions Steve Jobs asked at Apple. A product is what the culture produces when they fanatically focus on their customer.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
“Working Backwards” is Amazon's brilliant approach to product development.
We took this approach and applied it to product onboarding, the make or break phase of any product.
I’m sharing 3 core concepts of the onboarding, all qualitative in nature.
1. Parts
Parts are the knobs and settings on the TV or Radio device.
You know what they do when you touch them.
They are hard to design but even harder to name.
This is where most amount of iteration in product design happens in early days, and is worth the effort.
2. Sequence
Products automate jobs to be done for the user. Many impose a sequence of operation or sub-tasks to complete the job.
This sequence is never the same as user did outside your product or before your product.
Sequencing operation of the parts when good design helps.
Shipping a product is discipline, relentless iteration & prioritization.
Post COVID. The team met everyday, every morning, pouring through use cases, noisy data, screenshots, issues. Many iterations. And prioritized shipping over everything. (Even human touch).
I put mini team screen shot but it’s an amazing effort from every team member.
The product experience was the core goal for the initial shipping. It has to be easy to use. Simple to try.
UX copy is such big differentiator when making your product simple. So much focus goes in visuals that we miss the most important leverage in a product: good UX copy.
On b2b software: recollecting my experience using Slack, Salesforce CRM, Mailchimp, Hubspot, Atlassian, And one degree of separation Accounting/tax, Procurement. AWS, Databases, Zapier or Integrations, IDE. MS office. Wordpress. Canva. Analytics tools like BigQuery, Pandas
Not counting: Billing software, Support/help-desk software, Zoom/Skype, Social Media.
Getting leads isn't enough if you can't close deals, fast! #Sales Ops is a sales catalyst function in any growth company. But as I meet leaders at fast growing companies there continues to be frustration around lack of automation for #SalesOps.
A thread here on the same:
@CSOInsights
has mapped 4 broad functions of Sales Ops with 16 specific key activities :
1. Strategic Planning Support Activities 2. Sales Performance Analysis 3. Sales Readiness & Sales Cycle Support 4. Technology Management
Don’t overstack your sales stack.
Here is our latest blog on Building your sales stack which is aligned to buyer’s journey:
🔬 Research
🤵 Lead engagement
📑 Negotiation
💸 Deal closure
💓 Customer Success
1. Focus on prospecting tools which find you the right contact details. Provides details into prospect (revenue, headcount, competition) 2. We recommend conferencing & scheduling tools on @G2CrowdReviews. Look for fool proof scheduling and call recording features.
🤵Lead engagement
3. Streamline prospect interaction using right pitching tools 4. Build a objection handling repository in your CRM 5. Invest in tools that enable a great product demo
inspired by @HubSpot , @TweetSamG says "Sales Ops professional is akin to a coxswain for salespeople. They provide the guidance and direction needed by #sales team to meet and exceed targets" linkedin.com/pulse/your-sal…
To confuse between a tactical and strategic role hurts your hiring says @TweetSamG "A person geared to provide support is more tactical and will not have relevant problem-solving skills or analytical thinking required by a strategic function." linkedin.com/pulse/your-sal…