From 06ff610bad58f8fefaeb2be9bed75cfd65b738d7 Mon Sep 17 00:00:00 2001 From: lucaronin Date: Sat, 21 Feb 2026 11:53:39 +0100 Subject: [PATCH] content: enrich responsibility notes Co-Authored-By: Claude Opus 4.6 --- .../responsibility-content-production.md | 36 ++++++++++++++++--- .../responsibility-grow-newsletter.md | 31 +++++++++++++--- .../responsibility-health-fitness.md | 32 ++++++++++++++--- .../responsibility/responsibility-learning.md | 30 +++++++++++++--- .../responsibility-personal-finance.md | 33 ++++++++++++++--- .../responsibility/responsibility-podcast.md | 33 ++++++++++++++--- .../responsibility-sponsorships.md | 33 ++++++++++++++--- .../responsibility-team-management.md | 33 ++++++++++++++--- 8 files changed, 228 insertions(+), 33 deletions(-) diff --git a/demo-vault-v2/responsibility/responsibility-content-production.md b/demo-vault-v2/responsibility/responsibility-content-production.md index 75158e59..19a3c99b 100644 --- a/demo-vault-v2/responsibility/responsibility-content-production.md +++ b/demo-vault-v2/responsibility/responsibility-content-production.md @@ -7,8 +7,36 @@ Has Procedures: ["[[procedure-weekly-newsletter]]", "[[procedure-monthly-pillar- Status: Open --- # Content Production -Publishing weekly essays and newsletter editions. Maintaining high editorial quality while shipping consistently. -## KPIs -- Articles per week: 1 newsletter + 1 essay minimum -- Quality score: reader feedback >4.5/5 +Content production is the engine behind Refactoring. Every week, the newsletter and supporting essays need to ship on time, at a quality bar that keeps readers coming back. This responsibility covers the full lifecycle of written content — from ideation and outlining through drafting, editing, and publishing — and it is the single most important operational commitment in the business. + +## Scope + +- Writing and publishing the weekly Refactoring newsletter edition +- Producing standalone essays and deep-dive articles on engineering leadership topics +- Maintaining and executing the monthly content calendar and pillar plan +- Running A/B tests on subject lines, formats, and send times to optimize engagement +- Coordinating with [[person-sara-ricci]] on editorial review and copy quality +- Auditing and refreshing evergreen content to keep the archive valuable over time + +## Current state + +The production cadence is stable: one newsletter edition plus at least one standalone essay ships every week. Reader feedback consistently lands above 4.5 out of 5 on quality, and the editorial pipeline with Sara has reduced last-minute scrambles significantly. The main challenge right now is balancing depth with consistency — some weeks the essay ideas demand more research time than the schedule allows, which can push social distribution to the back burner. + +Pillar planning has helped front-load topic selection, but there is room to improve the feedback loop between [[measure-essay-quality-score]] data and future topic choices. The evergreen content audit is running quarterly but could benefit from being more systematic. + +## Key procedures + +- [[procedure-weekly-newsletter]] +- [[procedure-monthly-pillar-planning]] +- [[procedure-content-calendar-review]] +- [[procedure-editorial-review]] +- [[procedure-newsletter-ab-testing]] +- [[procedure-social-media-scheduling]] +- [[procedure-evergreen-content-audit]] +- [[procedure-newsletter-metrics-weekly]] + +## Key measures + +- [[measure-articles-per-week]] +- [[measure-essay-quality-score]] diff --git a/demo-vault-v2/responsibility/responsibility-grow-newsletter.md b/demo-vault-v2/responsibility/responsibility-grow-newsletter.md index 1e6fbb9f..374cfbab 100644 --- a/demo-vault-v2/responsibility/responsibility-grow-newsletter.md +++ b/demo-vault-v2/responsibility/responsibility-grow-newsletter.md @@ -7,8 +7,31 @@ Has Procedures: ["[[procedure-monthly-subscriber-metrics]]", "[[procedure-referr Status: Open --- # Grow Newsletter -Growing the Refactoring newsletter subscriber base through organic content, SEO, referrals, and strategic partnerships. -## KPIs -- Subscribers: target 100k by end 2025 -- Open rate: maintain >45% +Growing the Refactoring subscriber base is the highest-leverage activity in the business. Subscriber count directly drives sponsorship revenue, audience trust, and long-term brand equity. This responsibility covers every channel and tactic used to attract new subscribers and retain existing ones — organic search, referral loops, welcome sequences, and strategic cross-promotions. + +## Scope + +- Tracking and analyzing subscriber growth trends on a monthly basis +- Running and iterating on the referral program to turn readers into advocates +- Optimizing the welcome email sequence to convert new signups into engaged readers +- SEO optimization of published essays and newsletter archive pages +- Experimenting with cross-promotions and partnerships with complementary newsletters +- Monitoring open rate and engagement metrics as leading indicators of list health + +## Current state + +The newsletter is on a strong growth trajectory, with organic and referral channels accounting for the majority of new subscribers. Open rates remain well above industry average at over 45%, which signals a healthy, engaged list. The referral program is functional but underutilized — most readers do not actively share, and the incentive structure could be more compelling. + +SEO is an area with significant untapped potential. Several essays rank well for competitive long-tail keywords, but the back-catalog has not been systematically optimized. The welcome sequence converts well, though it has not been updated in several months and could benefit from fresh content that reflects the newsletter's current positioning. + +## Key procedures + +- [[procedure-referral-program]] +- [[procedure-welcome-email-sequence]] +- [[procedure-seo-content-optimization]] + +## Key measures + +- [[measure-subscribers]] +- [[measure-open-rate]] diff --git a/demo-vault-v2/responsibility/responsibility-health-fitness.md b/demo-vault-v2/responsibility/responsibility-health-fitness.md index 2b92b035..405405ae 100644 --- a/demo-vault-v2/responsibility/responsibility-health-fitness.md +++ b/demo-vault-v2/responsibility/responsibility-health-fitness.md @@ -7,8 +7,32 @@ Has Procedures: ["[[procedure-weekly-cycling-block]]", "[[procedure-gym-routine] Status: Open --- # Health & Fitness -Staying fit through cycling, gym, and good nutrition. Training for gran fondos and maintaining energy for work. -## KPIs -- Resting HR: <55 bpm -- Cycling: 300+ km/month in season +Health and fitness underpin everything else. Without consistent physical training and good recovery habits, writing quality drops, decision-making suffers, and energy for the business fades. This responsibility covers structured cycling training, gym work, nutrition awareness, and preparing for endurance events like gran fondos — treating the body as infrastructure, not an afterthought. + +## Scope + +- Following a structured weekly cycling training plan with volume and intensity targets +- Maintaining a consistent gym routine focused on functional strength and injury prevention +- Tracking resting heart rate and other biomarkers as proxies for overall fitness +- Preparing for specific endurance events and races throughout the season +- Conducting monthly health reviews to assess trends and adjust training load +- Balancing training volume with work demands, especially during high-output content weeks + +## Current state + +The cycling season is in full swing, and monthly volume is tracking at or above 300 km per month. Resting heart rate is holding in a good range, which suggests the aerobic base is solid. Gym sessions have been more inconsistent — they tend to get squeezed when the content calendar is packed, which is a pattern worth addressing. + +Race preparation for upcoming gran fondos is on track, but the transition between base-building and race-specific intensity blocks needs more deliberate planning. The monthly health review has been useful for catching overtraining signals early, though adherence to the review cadence has slipped a few times this year. + +## Key procedures + +- [[procedure-weekly-cycling-block]] +- [[procedure-gym-routine]] +- [[procedure-monthly-health-review]] +- [[procedure-race-preparation]] + +## Key measures + +- [[measure-resting-hr]] +- [[measure-cycling-km-per-month]] diff --git a/demo-vault-v2/responsibility/responsibility-learning.md b/demo-vault-v2/responsibility/responsibility-learning.md index 80c88a4a..f3777af7 100644 --- a/demo-vault-v2/responsibility/responsibility-learning.md +++ b/demo-vault-v2/responsibility/responsibility-learning.md @@ -7,8 +7,30 @@ Has Procedures: ["[[procedure-weekly-reading-session]]", "[[procedure-evergreen- Status: Open --- # Learning -Reading widely, studying deeply, and creating evergreen notes. Focused on non-fiction: business, technology, science, and self-improvement. -## KPIs -- Books per month: 2+ -- Evergreen notes: 3+ per month +Learning is the raw material supply chain for everything Refactoring produces. Reading widely, studying deeply, and synthesizing ideas into evergreen notes ensures that the newsletter and podcast draw from a genuine well of insight rather than recycled surface-level takes. This responsibility covers deliberate reading habits, note-taking systems, and the ongoing effort to turn consumption into durable knowledge. + +## Scope + +- Maintaining a consistent weekly reading practice across books, articles, and research papers +- Focusing reading on non-fiction domains: business strategy, technology, behavioral science, and self-improvement +- Writing evergreen notes that distill key ideas into reusable, linkable knowledge assets +- Curating a reading pipeline that balances current interests with deliberate exploration of new fields +- Connecting reading insights to content production — feeding ideas into newsletter essays and podcast topics +- Reviewing and refining the personal knowledge management workflow periodically + +## Current state + +The reading habit is consistent, averaging two or more books per month, with a good mix of business, technology, and science titles. Evergreen note output is meeting the target of three or more per month, though the quality and depth of notes varies — some are thorough syntheses, others are closer to quick highlights that need revisiting. + +The main gap is in the connection between reading and production. Many good ideas from books end up buried in notes without surfacing in newsletter content or podcast conversations. Building a better bridge between [[procedure-evergreen-note-writing]] and [[procedure-monthly-pillar-planning]] would help close this loop and make the learning investment pay off more directly. + +## Key procedures + +- [[procedure-weekly-reading-session]] +- [[procedure-evergreen-note-writing]] + +## Key measures + +- [[measure-books-per-month]] +- [[measure-evergreen-notes-created]] diff --git a/demo-vault-v2/responsibility/responsibility-personal-finance.md b/demo-vault-v2/responsibility/responsibility-personal-finance.md index 7078c4ac..4eb7b1a6 100644 --- a/demo-vault-v2/responsibility/responsibility-personal-finance.md +++ b/demo-vault-v2/responsibility/responsibility-personal-finance.md @@ -3,12 +3,35 @@ aliases: ["Personal Finance"] Is A: Responsibility Belongs to: "[[area-finance]]" Has Measures: ["[[measure-net-worth]]", "[[measure-savings-rate]]"] -Has Procedures: ["[[procedure-monthly-portfolio-review]]", "[[procedure-quarterly-financial-planning]]"] +Has Procedures: ["[[procedure-monthly-portfolio-review]]", "[[procedure-quarterly-financial-planning]]", "[[procedure-invoice-processing]]"] Status: Open --- # Personal Finance -Managing investments, savings, and financial planning. Building long-term wealth through index funds and diversification. -## KPIs -- Savings rate: >30% of income -- Net worth: track monthly +Personal finance is about building long-term financial resilience so that creative and business decisions are never driven by short-term cash pressure. This responsibility covers investment management, savings discipline, financial planning, and the operational side of invoicing and cash flow — all with a philosophy rooted in simplicity, index fund investing, and a high savings rate. + +## Scope + +- Tracking net worth on a monthly basis to maintain visibility into long-term trajectory +- Maintaining a savings rate above 30% of income through disciplined spending +- Managing an investment portfolio primarily built on low-cost index funds +- Running quarterly financial planning sessions to review goals, allocation, and risk +- Processing invoices and managing cash flow for Refactoring's sponsorship revenue +- Keeping financial systems simple and automated wherever possible + +## Current state + +The savings rate target is consistently met, and the portfolio is performing in line with broad market indices. Monthly net worth tracking has become a reliable habit, and the quarterly planning sessions provide a good checkpoint for rebalancing and revisiting assumptions. Invoice processing runs smoothly thanks to a standardized workflow, though there is occasional lag when sponsor renewals overlap. + +The main area for improvement is tax optimization. As Refactoring's revenue grows, the Italian tax situation becomes more complex, and there may be opportunities to structure things more efficiently. This is worth a dedicated review in the next quarterly planning session. The overall philosophy remains unchanged: keep it boring, keep it diversified, and let compounding do the work. + +## Key procedures + +- [[procedure-monthly-portfolio-review]] +- [[procedure-quarterly-financial-planning]] +- [[procedure-invoice-processing]] + +## Key measures + +- [[measure-net-worth]] +- [[measure-savings-rate]] diff --git a/demo-vault-v2/responsibility/responsibility-podcast.md b/demo-vault-v2/responsibility/responsibility-podcast.md index 5e2c1984..a19b1e4d 100644 --- a/demo-vault-v2/responsibility/responsibility-podcast.md +++ b/demo-vault-v2/responsibility/responsibility-podcast.md @@ -7,8 +7,33 @@ Has Procedures: ["[[procedure-podcast-recording]]", "[[procedure-podcast-guest-o Status: Open --- # Podcast -Running the Refactoring podcast — bi-weekly episodes with tech leaders on engineering culture, leadership, and building. -## KPIs -- Downloads per episode: target 5k+ -- Episodes per month: 2 +The Refactoring podcast is the second major content channel alongside the newsletter. Bi-weekly episodes featuring conversations with tech leaders, engineering managers, and founders create a different kind of depth and relationship than written content alone. This responsibility covers the full production pipeline — guest sourcing, recording, editing, publishing, and performance analysis — and plays a critical role in audience growth and brand positioning. + +## Scope + +- Sourcing and scheduling guests who bring genuine insight on engineering culture, leadership, and building +- Preparing for and conducting interviews that are conversational, substantive, and worth re-listening to +- Managing the post-production pipeline: editing, show notes, and publishing on schedule +- Tracking downloads and engagement metrics to understand what resonates with the audience +- Maintaining a guest pipeline that is at least 4-6 weeks ahead of the publishing calendar +- Cross-promoting episodes through the newsletter and social channels to maximize reach + +## Current state + +The podcast is shipping consistently at two episodes per month, and download numbers are trending upward. Guest quality has been strong, with several recent episodes generating above-average engagement and social sharing. The production pipeline with [[person-paco-furiani]] handling operations has reduced the turnaround time from recording to publication significantly. + +The main challenge is guest pipeline management. Outreach tends to happen in bursts rather than steadily, which occasionally creates scheduling pressure. There is also an opportunity to be more strategic about guest selection — aligning episode topics with upcoming newsletter themes to create a more cohesive content ecosystem. Analytics review happens but is not yet systematic enough to drive data-informed decisions about format and topic selection. + +## Key procedures + +- [[procedure-podcast-recording]] +- [[procedure-podcast-guest-outreach]] +- [[procedure-podcast-editing]] +- [[procedure-podcast-show-notes]] +- [[procedure-podcast-analytics]] + +## Key measures + +- [[measure-podcast-downloads]] +- [[measure-podcast-episodes-per-month]] diff --git a/demo-vault-v2/responsibility/responsibility-sponsorships.md b/demo-vault-v2/responsibility/responsibility-sponsorships.md index 9b51556d..221eae0b 100644 --- a/demo-vault-v2/responsibility/responsibility-sponsorships.md +++ b/demo-vault-v2/responsibility/responsibility-sponsorships.md @@ -7,8 +7,33 @@ Has Procedures: ["[[procedure-monthly-sponsor-report]]", "[[procedure-quarterly- Status: Open --- # Sponsorships -Selling and managing sponsorships for Refactoring. Building long-term relationships with B2B tech companies. -## KPIs -- MRR: grow from €8k to €22k -- Close rate: maintain >30% +Sponsorships are the primary revenue engine for Refactoring. Selling and managing sponsorship deals with B2B tech companies funds the entire operation — from team salaries to tools to the time and space needed for quality content production. This responsibility covers the full sponsorship lifecycle: outreach, closing, onboarding, delivery, reporting, and renewal. The goal is to build long-term partnerships, not one-off ad placements. + +## Scope + +- Running quarterly outreach campaigns to fill the sponsorship pipeline with qualified prospects +- Closing sponsorship deals with a focus on long-term, recurring partnerships over one-off placements +- Onboarding new sponsors with clear expectations on deliverables, timelines, and audience data +- Delivering monthly sponsor reports that demonstrate value and ROI transparently +- Managing renewals proactively, using performance data and relationship quality to retain sponsors +- Coordinating with [[person-matteo-cellini]] on partnership strategy and outreach execution + +## Current state + +Sponsorship revenue is growing steadily, with MRR on a clear upward trajectory from its current base toward the target. Close rate remains healthy at above 30%, and the renewal pipeline is strong — most sponsors who run a first campaign choose to continue. The relationship-first approach, grounded in the philosophy captured in [[the-sponsorship-relationship]], is paying off. + +The biggest bottleneck is outreach volume. Quarterly outreach cycles sometimes lose momentum in execution, and there is an opportunity to systematize the pipeline further with [[person-matteo-cellini]] owning more of the top-of-funnel work. Sponsor reporting has improved significantly but could be more automated. The invoice processing workflow is reliable but still involves some manual steps that are worth streamlining. + +## Key procedures + +- [[procedure-quarterly-sponsor-outreach]] +- [[procedure-sponsor-onboarding]] +- [[procedure-sponsor-renewal]] +- [[procedure-monthly-sponsor-report]] +- [[procedure-invoice-processing]] + +## Key measures + +- [[measure-sponsorship-mrr]] +- [[measure-close-rate]] diff --git a/demo-vault-v2/responsibility/responsibility-team-management.md b/demo-vault-v2/responsibility/responsibility-team-management.md index eaac2dfe..e99b9b14 100644 --- a/demo-vault-v2/responsibility/responsibility-team-management.md +++ b/demo-vault-v2/responsibility/responsibility-team-management.md @@ -7,8 +7,33 @@ Has Procedures: ["[[procedure-weekly-team-sync]]", "[[procedure-biweekly-1on1-ma Status: Open --- # Team Management -Managing Matteo (partnerships), Paco (operations), and Sara (editor). Building a small but high-performing team. -## KPIs -- Team NPS: >8 -- Task completion rate: >85% +Team management is about getting the most out of a small, high-trust team without introducing the overhead and bureaucracy that kills small operations. With [[person-matteo-cellini]] on partnerships, [[person-paco-furiani]] on operations, and [[person-sara-ricci]] on editorial, the team is compact but covers the critical functions of the business. This responsibility encompasses hiring decisions, task coordination, performance feedback, and building a culture where people do their best work with minimal friction. + +## Scope + +- Running weekly team syncs to align priorities, surface blockers, and maintain shared context +- Conducting biweekly 1:1s with each team member to provide feedback, coaching, and support +- Tracking task completion rates to ensure operational commitments are met consistently +- Running quarterly retrospectives to reflect on what is working and what needs to change +- Making decisions about team structure, roles, and potential new hires as the business grows +- Maintaining team morale and engagement, measured through internal NPS and qualitative signals + +## Current state + +The team is functioning well. Weekly syncs keep everyone aligned, and the biweekly 1:1 cadence provides enough touchpoints to catch issues early. Task completion rate is above target, and the overall vibe is positive — people feel ownership over their domains and have the autonomy to make decisions within them. + +The main area to watch is scaling. As Refactoring grows, the current team structure will come under pressure. Matteo is increasingly stretched across partnerships and sponsor outreach, and there may be a case for additional support there. The quarterly retro has been valuable for surfacing these kinds of structural questions before they become urgent. The philosophy outlined in [[small-teams-scale-through-systems]] guides how the team thinks about growth — systems and processes first, headcount second. + +## Key procedures + +- [[procedure-weekly-team-sync]] +- [[procedure-biweekly-1on1-matteo]] +- [[procedure-biweekly-1on1-paco]] +- [[procedure-biweekly-1on1-sara]] +- [[procedure-quarterly-team-retro]] + +## Key measures + +- [[measure-team-nps]] +- [[measure-task-completion-rate]]