Newsletter Category Creator
Positioning work for the newsletter project, working through the category creator framework to find the right niche, problems, outcomes, and one-liner.
Newsletter Positioning Checklist
-
An Information Advantage: You should have picked a topic and industry you have experience in and know well. (Again, you don’t have to be an “expert” by any means, but you should have some level of experience.)
- I have expertise in data engineering and data modeling with business analytics. I have delivered specific results from Attribution to Retention.
-
Genuine Curiosity: You also should have picked a topic you are excited to keep learning about, and writing about, for a consistent period of time. (Again, doesn’t have to be forever, but also shouldn’t be “3 weeks.”)
- Yes, I enjoy practicing my craft. See 06-reference/concepts/analytics-as-craft.
-
Your niche topic “niched-down-further” in one of the 9 ways: By experience level, revenue level, platform/tool, digital or analog location, gender/age/demographic, event/status/identity, career path/job title, problem, or desired outcome.
- Talking to data leads delivering for executives grounded in deliverables.
-
A list of Problems you’re excited to solve, and Outcomes you’re excited to help these readers unlock: And my recommendation is to pick 1 Problem and 1 Outcome to really anchor your newsletter around. (This doesn’t mean you can’t write about the others. But it helps to “lead with 1.”)
- Yes - see below
-
All put together in a “1-Liner” description: Topic + “niche-down-further” + 1 problem + 1 outcome. (Or, you can flip them: Topic + “niche-down-further” + 1 outcome + 1 problem.)
- I write about how business event data modeling can uncover the causal model of a company and unlock growth opportunities, cementing the data team’s place as a profit center.
- I help data teams deliver the executive “most valuable meeting” weekly through business event data modeling.
-
Tangible, not Intangible Language: Now, do a couple rewrites to make sure your 1-Liner is as Tangible as possible. Don’t forget to use one of the 20 “Tangible” ways I gave you.
- Done
-
Objective, not Subjective Language: After that rewrite, stress-test it by making sure your promises are Objective (not Subjective and “open to interpretation”).
- Done - could iterate on again
-
Name Your Newsletter: Now, give it a main title that is CLEAR… not “Clever.” And make it as Tangible as possible.
- Execute with Analytics
Niche Drill-Down
- Analytics
- Event Analytics
- Event Analytics for Data Leads
- Event Analytics
10 Problems
- Spaghetti code / tech debt
- Buried in stakeholder requests / ticket mill
- Balancing priorities
- Unreliable data sources / data quality
- Maintaining stakeholder trust in the data
- Inadequate data infrastructure
- Data governance / rogue data teams / silos
- Building and retaining the data team
- Data documentation / discovery / dissemination
- Data downtime / broken pipelines
10 Desirable Outcomes
- WBR support
- Marketing Attribution
- Bookings / Sales Quota
- Retention Analysis
- Frequent usage of dashboards / reports
- Uncovering the causal model of their business
- Metrics and definition alignment across functional teams
- Reliable data pipelines that alert data quality issues before being caught by stakeholders
- Bonus - this protects stakeholder trust
- Forecasting / Budgets / Annual Planning
- Operational Support and analysis
- Mastery of Craft
- Promotion / Prestige / Organizational Impact
These problems and outcomes directly connect to the open knowledge sharing philosophy — sharing recipes, not secrets.
Alternate Name Explorations
- Business model teardowns
- Specific analytics workloads (Attribution, SaaS Retention / Cohorts)
- Puzzles / Board Games
- Signal Craft — Data Foundations & Use Cases