š Hello and welcome to this weekās edition of āØĀ Community Wisdom ⨠ā a weekly email highlighting the most helpful advice fromĀ our subscriber [[Slack]] community. As always, aĀ bāiāg thank you toĀ [Kiyani](https://www.linkedin.com/in/kiyanibamba?originalSubdomain=ca)Ā for pulling this email together.
#### š„ Top threads thisĀ week
1. SEO keyword prioritization 2. Career ladders for PMs 3. Backlog tools 4. Tools for scheduling user interviews 5. Building an āidea-repositoryā
#### š¤ Top reads and listens
1. Improving your copywriting 2. OnlyFans and the creator economy 3. Measuring SaaS Engagement
#### š¤ AMA with Pete Kazanjy (about sales)
1. Learning how to do sales 2. Managing lead flow 3. Sales as an introvert 4. Self-serve product experience 5. Frameworks for doing large enterprise sales
š„ Top threads thisĀ week
1. SEO keyword prioritization
Q: We've started in SEO and itās been one month now, but we are facing some friction on prioritizing keywords. Our keyword prioritization process currently looks like this:
>
1. Gathered thousands of keywords based on important keyword seeds to our business. 2. Populated these lists with data on search volume, search difficulty and CPC (as a proxy for high commercial intent). 3. Prioritize keywords. 4. Build content on those keywords.
>
The problem is in step 3: which parameter (volume, CPC, difficulty) should we give more importance in T0 since we are justing starting (have a low domain score) and need to convert ASAP? Is there any way of quantitavely prioritize these keywords?
>
āĀ [Caique Carvalho](https://www.linkedin.com/in/caique-carvalho-b39295106/)
[Nima Gardideh](https://twitter.com/ngardideh): One tactic I've seen is using AdWords first and then looking at conversion rates to prioritize the keywords for SEO. i.e. if you have 50 keywords:Ā pay for the clicks first and see which ones bring in high-quality customers. Then go build search optimized pages to capture the traffic without having to pay for it.
[Chris Toy](https://twitter.com/christoy): Fix domain authority as the priority. The rest is a multiple on zero until you do. If you donāt fix domain auth, you can only target extremely niche or uncompetitive keywords.
[Yair](https://www.linkedin.com/in/yairlivne/): One other comment is that framing SEO as something that can convert immediately is fundamentally off. It takes at least 6 months to start seeing payoffs, and the right mindset here is long term.
[Jeff](https://twitter.com/jfedor): What are the best ways to increase Domain Authority?
Katie Mitchell: Quality backlinks and making sure your site runs fast, etc.
[Yair](https://www.linkedin.com/in/yairlivne/): Also being strong in a domain of knowledge, not just a lot of mediocre content across domains.
[Brian Ta](https://twitter.com/fanfavorite_bta) : Iām going to run counter to everyone here:
- Domain authority isnāt a good use of your time to focus on. Youāll build it over time. Also worth noting that the number you see for domain authority is a made-up metric number that ahrefs or whatever tool youāre using calculated.
- Forget backlinks. Iāve worked with a number of sites, and Iāve never seen a positive correlation between backlinks and an increase in organic trafficĀ that can be attributed directly to backlinks. Focus on your content.
- Iāve seen SEO pay off in a month. If it doesnāt pay off in 3 months, then itās worth revisiting your strategy.
- Iāve always run keywords by the eye test. If the other content on the page looks bad and you can create something better, then go for it.
- If I was really pushed, Iād target for under 1000 first, once you prove it out, you can target the higher volume keywords.
- Generally, the lower volume/longer tail keywords will lead to high conversions because the user is further down the funnel. (āflower shopā versus āwhere to buy flowers in Burbankā)
- High-quality content is whatās going to make you win. Most other things are secondary.
- Make sure your site has its SEO foundations set.
[Chris Toy](https://twitter.com/christoy): I think good content is table-stakes ā bad content gets you nowhere. Domain authority isnāt and is often overlooked, which is why I think peeps are focused on it. If you want SEO to be your backbone with results early enough to affect an early-stage startup (as it sounded like this was) then domain authority is probably going to be your issue. If youāre a high-growth startup with traffic coming from other places then yes you can afford to wait.
I have seen grey/black hat backlinking attributed to SEO gains consistently over the last decade, was the original āhackā. But agree with the restĀ @Brian Ta!
[Brian Ta](https://twitter.com/fanfavorite_bta): Iāve helped a number of startups go from 0 to 100k a month with low 20s in their domain authority. Iāll have to respectfully disagree with you on needing to focus on domain authority.Ā Domain authority is the result of creating good content, getting traffic, and accruing links over time. Domain authority is a magic number that some engineer or SEO dreamed up of. Itās not the number that Google sees your site on. Optimizing for DA is optimizing for this magic number.
Whatās always worked is: good content and a good SEO strategy.On backlinks: I havenāt seen any startup or company thatās invested in a backlink strategy that could be directly attributed to their growth in SEO. Iāve seen many attempt it, and none of them have worked. If someone wants to attempt to do black hat link building, it \_might\_ work until the time bomb ticks down and Google hands you down a manual penalty.
I have quite a few clients that go the link building route, after we get their site to an acceptable state. 4 months later, without fail, they come back and say it was a waste of time and they didnāt see any measurable uptick in traffic.
[Chris Toy](https://twitter.com/christoy): @Brian TaĀ I think what weāre all saying is SEO is a lot of work and you have to do all of it. Good content to build DA over time is still DA, and you canāt just do DA with garbage content. Itās not a single variable thing.
[Brian Ta](https://twitter.com/fanfavorite_bta): Closing the loop. Iām talking to Chris on DMs but wanted to surface part of the convo.
I'm going to push a little further on getting links. How many times have you done link building on an article and it hasn't worked? Would the content perform the same if you hadn't gotten links to it? I find that a lot of people will look at the number of backlinks a website has, see that they get a lot of traffic, and make the conclusion that backlinks help with more traffic. Iāve seen lots of websites where theyāve invested in tons of backlinks and gotten no return on it. The way that SEO case studies are broken down lends itself to survivorship bias. No one is breaking down how a no-name website didnāt achieve SEO. There arenāt companies bragging about how their SEO strategy didnāt pan out and that backlinks didnāt work. We usually see a company that has a lot of SEO success, and automatically assume that everything they did contributed to that success.
What makes teasing apart backlink impact difficult, is that most companies are working on both backlinks and other large SEO fixes at the same time. Whatās to say the big impact isnāt from the normal SEO stuff that you did and the links havenāt had much, if any, impact? You could make the argument that itās the other way around, SEO fixes did nothing and backlinks did all of the work, but Iāve run enough SEO experiments to know that basic fixes for sure have an outsized impact.
Anyway, those are my thoughts on backlinks and how they relate to SEO. Itās nice to have when you get it, donāt spend extra energy to build it out. You have a finite amount of time to spend on SEO, Iād much rather spend it on content creation than backlinks.
2. Career ladders for PMs
Q: Anybody have any great examples of a career ladder/lattice for the various levels of product manager? e.g. Junior, Intermediate, Senior, Lead, etc. Shreyasā mind map is a great start in defining the skill categories but Iām curious if thereās anything out there that outlines the expected level of competency in each category as you progress.
>
āĀ [Wayne Vernon](https://twitter.com/wplusv)
[Wayne Vernon](https://twitter.com/wplusv): Mind map in question

[Ben Ritchie](https://www.linkedin.com/in/benritchie1/): I really like Ravi Mehta's product competency approach. He introduces his framework here but the full guide has a rubric for the skill level at each seniority: Whatās Your Shape? A Product Managerās Guide to Growing Yourself and Your Team
[Amit](https://www.linkedin.com/in/amitjklein/): I've used this in the past as a starting point for self-assessments for PMs:Ā Product Manager Skills by Seniority LevelāāāA Deep Breakdown
Lenny Rachitsky: Here are a bunch Iāve found (from this older post):
1. [Intercom](https://blog.intercomassets.com/blog/wp-content/uploads/2019/05/Intercom-PM-job-ladder-Logo.pdf) 2. Oscar 3. Gusto 4. XO Group 5. Gitlab
[Archisman Das](https://twitter.com/archismandas): There is a great write up by Sachin Rekhi on this. You can find it here - Product Management Career Ladders at 8 Top Technology Firms.
I also did this exercise for my time a while back and you can find it here. Although, I'm planning to revisit it again and looking forward to inputs on this thread.

3. Backlog tools
Q: Who here has discovered a way of organizing their backlog that theyāre pretty happy with? We're migrating ours to Asana, and starting fresh! Curious what kinds of mental models or frameworks folks here have found success with
>
āĀ [Kali Borkoski](https://www.linkedin.com/in/kali-borkoski-998082171/)
[Wayne Vernon](https://twitter.com/wplusv): At a super high level, my backlog goals are:
1. Development work only that is in a workable stage, i.e. can be picked up a ran with by a dev based on the information in the ticket 2. If itās dev work butĀ notĀ ready to be worked on, consider setting up an Icebox so your team can ignore it but you donāt lose it 3. If itās not dev work but an idea, feature request, etc. instead, it should live somewhere other than your backlog. Plus, schedule intentional time to groom your backlog.
I used to try to do this as part of other ceremonies but it never really worked out. Now I have 30 minutes every 2 weeks where myself, my leads, and QA sort the backlog by last activity and work through closing, updating, etc. as many tickets as possible. Itās infrequent and short enough to not be painful but enough to slowly chip away at all the noise.
[Kali Borkoski](https://www.linkedin.com/in/kali-borkoski-998082171/): Thank you,Ā @Wayne Vernon! What do you do with the tickets that fall in bucket #3?
[Wayne Vernon](https://twitter.com/wplusv): I personally maintain my own list in a doc (Confluence for us) that I prioritize and add context to. There are definitely better ways to do this, e.g. most product management tools handle feature ideas and requests more natively. Really depends on your ācustomerā and how visible you need to make these things. For me, Iām not super worried about it so a doc works fine.
[Yair](https://www.linkedin.com/in/yairlivne/): At Quora we use Asana for tracking backlogs. Each team has its own backlog "project" where tasks are tracked. Teams usually have some cadence where the PMs/eng managers might go through the backlog tasks, reprioritize / potentially delete some / potentially just crank a few out. This is particularly useful ahead of weeks where we focus on product/tech debt and there's time to plow through a bunch of these.
[Kali Borkoski](https://www.linkedin.com/in/kali-borkoski-998082171/): @Yair, Thank you! What are the fields you've added to that Asana board? (Priority, effort, etc?)
[Yair](https://www.linkedin.com/in/yairlivne/): This was team-by-team, but I do think almost everyone has priorities, as well as topical tags.
[Karri Saarinen](https://twitter.com/karrisaarinen): We are makers ofĀ Linear. Our framework is that you add all the new work to the backlog which means thatās only an idea but not committed work yet. Then you can have priorities or a few different categories like icebox, backlog, next that categorize generally how relevant this work is. Then for each cycle (sprint) we just select the work from the backlog to be worked on next.
Overall we donāt worry or groom the backlog too much, we just add stuff and then in the cycle planning select what is relevant to work on next. So backlog is the dump of all the possible work we could do, and cycles define what we actually do. With that thinking you donāt need spent time organizing everything perfectly in the backlog, especially because most of it doesnāt ever get done.
We also have a feature that autocloses issues after x months so the backlogs donāt get infinite. If an issue or bug doesnāt get done in 6mo, it likely never gets done and if itās important, it will surface again.
Gaurav Chandrashekar: @Wayne,Ā don't you have backlog grooming as part of the sprint ceremonies?
[Wayne Vernon](https://twitter.com/wplusv): @Gaurav,Ā we follow a fairly casual implementation of agile at our org that is closer to Kanban than anything. Some like to have the ābacklog groomā and pre-planning for the next sprint(s) be one and the same. Some alternate these week to week. Iāve personally had better luck setting aside completely separate time where we do nothing but try to revise/expand/close/prioritize old tickets in the backlog.TLDR: Iām not an agile expert or advocate. I generally take a high-context approach where I do what I feel will get the best results from the team and product Iām working with at the time. And Iām fortunate to work in an org that supports this approach.
4. Tools for scheduling user interviews
Q: Who has a tool they like for scheduling/coordinating user interviews? We're looking at UserTesting but would love alternatives.
>
āĀ [Josh](https://twitter.com/herzigma)
[Manuel Bruschi](https://twitter.com/ttrauser): We use Calendly as a team with a round-robin assignment.
Tanmayi Sai: I use thisĀ [Lookback](https://lookback.io/) after switching over from User Interviews. It's also good for unmoderated tests.
Scott Stenback: Hi Josh - I know a founder who is building a new product around improving the scheduling experience. Let me know if you'd like a connection:Ā <https://www.buildbetter.app/>
5. Building an āidea-repositoryā
Q: Does anyone have a cool template for an āidea-repositoryā? Iām rotating to a new team and after talking with the UX teams Iāll be working with, they mentioned sometimes the ideas they propose in the projects get lost. Iām looking for some template or dynamic to tease this out. Something simple and clean that would allow everyone to express their view. Iām extremely interested in the ideas that come from UX teams.
>
āFranco
[Josh](https://twitter.com/herzigma): What tools do you use to capture ideas from other stakeholders, like user requests or executive requests? If you have a tool like that, then that's one good place.
If your only tool (i.e., a tool that gets used and worked actively and on a daily basis) is your backlog tool (like Jira) then I'd schedule a couple of hours for brainstorming and prioritizing meeting. The diverge/converge framework from design sprints is pretty good for this. And then just prioritize their feedback for the backlog.
Is this with the team you're rotating off or rotating on to? Either way might be nice to have the other PM (who you're replacing or who is replacing you) participate.
Sebastian Leon: Agreed with Josh, integrating idea-collection into an existing workflow is key!
Ultimately, you need a list that anyone can add to, with 2 items per idea: 1) quick description, 2) link to doc with more context (optional). This can be done in Jira, Google Spreadsheets, Notion, etc. Anytime someone brings up an idea, ask them to add it to the list.
For item 2), ask your team to fill out one of these templates (link). Itās actually pretty nice when backlog items are developed and matured over time, so that once it makes sense to prioritize it, a lot of the product thinking & interesting decisions have already been done.
š¤ Top reads and listens
1. Improving your copywriting
[Henrique Cruz](http:/twitter.com/HenrM_Cruz):
- Book: On Writing Well,Ā timeless advice about writing William Zinsser. Short review of the book.
- Tips from Amazon:

[Saushank](https://www.linkedin.com/in/saushank/): Nobody wants to read your ebook. Also, this course was quite good: Copywriting For Beginners: How To Write Web Copy That Sells Without Being Cheesy.
[Ben Ritchie](https://www.linkedin.com/in/benritchie1/): It's not a book but two things that might help:
1. First one is that the messaging is far more important than the exact wording so map out the benefits across multiple levels of abstraction and figure out the right level to speak to each audience with e.g. Analytics tool has better automation functionality -> You can finish all of your reporting faster -> You can spend more time on more strategic tasks. 2. The second thing is this podcast episode which is really good at exploring the different ways to add emotional hooks to the same offer: Episode 33: The Ad Grid: How to Build Campaigns that Convert and Scale - DigitalMarketer
2. OnlyFans and the creator economy
[Jayme](https://twitter.com/jaymehoffman): Awesome thread on OnlyFans and creator economy fromĀ @Peter Yang
3. Measuring SaaS Engagement
[Joe Magee](https://twitter.com/KJMagee): Great piece for Saas founders out there on how to think about āengagementā in a bottoms-up GTM:Ā [Measuring SaaS Engagement](https://sacks.substack.com/p/measuring-saas-engagement).
š¤ AMA with Pete Kazanjy (about sales)
1. Learning how to do sales
Q: Maybe not such a good question... Have you read Demand Side Sales? If so curious what you think. If not, itās basically Jobs To Be Done product theory applied to sales. Iād like to understand how people (you) educate themselves around sales, because like product management, you canāt really āgo to school for itā
>
ā [David Krell](https://www.linkedin.com/in/david-m-krell-508a3331/)
[Pete Kazanjy](https://www.linkedin.com/in/kazanjy/): I haven't read Demand Side sales, but sounds great! You're right that there isn't a "sales degree" per se, and that's in part what makes it challenging to learn later in your career, as most of the knowledge is learned via apprenticeship.
I learned a lot via First Round's Network, which was an early peer education community, which inspired me to create Modern Sales (<https://modernsaleshq.com/>) which is the sales operations and leadership community my company, Atrium, runs. 20k people. But peer education is key.
And then lastly ongoing learning of course is important. This is why I wrote Founding Sales - to reduce the learning curve:Ā <https://www.foundingsales.com/>. Other great books are:
- Cracking the Sales Management Code
- The Transparency Sale
- The Challenger Sale
- To Sell Is Human
- Persuasion by Robert Cialdini
2. Managing lead flow
Q: What systems \ process have you seen best for managing lead flow? Lotās of clients signup, some should have sale engage. What is the best systems for pushing the right leads over to Sales?
>
ā [Ali Javid](https://twitter.com/meetalijavid)
[Pete Kazanjy](https://www.linkedin.com/in/kazanjy/): Depends on the volume, but check out this chapter on "Inbound Marketing" from [Chapter 6 - Early Inbound Marketing: Inbound Lead Capture & Response - Startup Inbound Basics ā Founding Sales](https://www.foundingsales.com/6-inbound-marketing)
The first step is to have a mechanism by which to capture signups and hand raising. Having a "Contact Sales" button on the home page, even if it's a bootie mailto: link is important, but the more sophisticated version is to have a lead form that flows into your CRM. For Self-Serve, we talked about this a LOT in the post I wrote for Lenny's newsletter, but getting signup data into a CRM in some capacity, usually via a syncing tool like Census (Segment => Redshift / Snowflake => Hubspot CRM / Salesforce etc.) is powerful. You want to get the leads into a place where a human can prioritize them/triage/act.
3. Sales as an introvert
Q: Iāve always felt like folks who are good at sales are extroverted⦠do you know of more introverted people doing well in sales also? If so, what helps them succeed and there are any āclassic introvertā traits that are actually an advantage?
>
ā [Kara Skrip](https://www.linkedin.com/in/karaskrip/)
[Pete Kazanjy](https://www.linkedin.com/in/kazanjy/): Definitely. I talk about this some in this deck, starting at this slide:Ā Founder Led Selling Maturity Stages - Founding Sales. In short, yeah, you can see why someone who's extroverted would take more naturally to a task that requires to talk to lots of people they don't know.
That said, the way I like to describe "modern salespeople" is as "consultants who happen to have a predisposition to one particular solution (theirs)".
So analysis, writing, math, logic, argumentation, etc. all really becomes key there. And being good at those things is way more important than just being "fun." But getting good at / comfortable with selling behaviors does indeed require work, and you just build those muscles over time through lots of repetition.
More here: Chapter 1 - Mindset Changes: Startup Sales Mindset Changes ā Founding Sales
[Kara Skrip](https://www.linkedin.com/in/karaskrip/): Yeah I can see the "doing your homework" or prep portion of the job being really good for introverts
[Pete Kazanjy](https://www.linkedin.com/in/kazanjy/): "Doing your homework" (pre-call planning, proposal creation, etc.) is where a huge amount of the work is done.
4. Self-serve product experience
Q: Hi Pete - in your post you talked about āis the product simple enough for self-serve?ā - how do you differentiate between ānot an easy product to useā versus a product that is just poorly designed? My gut is complexity of product does not necessarily = poor user experience. Can you talk a bit about this? Thank you in advance!
>
ā Anonymous
[Pete Kazanjy](https://www.linkedin.com/in/kazanjy/): This is really more of a product question, really, but I think that there's a linear relationship between the complexity of a problem being solved and the complexity of an associated solution. With great product and engineering effort you can of course abstract that away with elegance and simplicity, but the more complicated the problem, probably the more engineering and product effort to do so. So I think the point here is that you should be mindful of this, and be honest when looking at your activation metrics to see if you are indeed getting there with self-serve - and if not...maybe it needs more human earlier.
5. Frameworks for doing large enterprise sales
Q: Hi Pete - are there any frameworks / processes that you recommend for doing large enterprise sales i.e. complex, lots of stakeholders, very intensive but large ACV? For example, does value based selling really work where you try and break down the solution into granular cost saving or revenue generating items to discuss with prospects.
>
ā [Nawaz Imam](https://twitter.com/nazking15)
[Pete Kazanjy](https://www.linkedin.com/in/kazanjy/): @Nawaz,Ā are you talking about top-down enterprise selling?
[Nawaz Imam](https://twitter.com/nazking15): I'm guessing it could either be top down or bottom up depending on the type of organisation? Seems most likely to be top down though.
[Pete Kazanjy](https://www.linkedin.com/in/kazanjy/): For those larger orgs, being crisper about deal modeling, using a methodology like MEDDIC, for example, can be helpful:Ā Close more deals with the MEDDIC sales process.
Thatās it for this week š
If thereās anyone in your life who would benefit from this newsletter or community, consider giving themĀ aā āgāiāfātĀ subscriptionš
Sincerely,
Kiyani and Lenny š