<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Projan Blog</title><description>Projan turns the messy Slack and Teams discussion of a feature into a clean PRD, acceptance criteria and tickets in Jira, Notion, Linear and ClickUp, so the PM doesn&apos;t spend an evening writing it up.</description><link>https://projan.ai/</link><language>en-gb</language><item><title>How to Write an RFP Response That Wins Agency Work</title><link>https://projan.ai/blog/how-to-write-an-rfp-response-that-wins-agency-work/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-write-an-rfp-response-that-wins-agency-work/</guid><description>What should be included in an RFP response? The sections evaluators score, how long you get, who writes what, and when to walk away from the bid instead.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate><category>rfp response</category><category>agency new business</category><category>bid management</category><category>client proposals</category><category>go no-go decision</category><author>Dave Clissold</author></item><item><title>Statements of Work for Agencies: Structure, Signatures, and Scope Protection</title><link>https://projan.ai/blog/statements-of-work-for-agencies-structure-signatures-and-scope-protection/</link><guid isPermaLink="true">https://projan.ai/blog/statements-of-work-for-agencies-structure-signatures-and-scope-protection/</guid><description>How do you write a statement of work? An agency guide to SOW structure, exclusions that hold up, change control, and the signature that actually counts.</description><pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate><category>statement of work</category><category>scope creep</category><category>change control</category><category>agency operations</category><category>client contracts</category><author>Dave Clissold</author></item><item><title>How to Run an OKR Planning Session That Ends in Commitment</title><link>https://projan.ai/blog/how-to-run-an-okr-planning-session-agenda-limits-and-getting-real-commitment/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-run-an-okr-planning-session-agenda-limits-and-getting-real-commitment/</guid><description>How to run an OKR planning session: a working agenda, how many OKRs a team should really carry, and how to close with named owners and a check-in date.</description><pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate><category>okrs</category><category>goal setting</category><category>planning sessions</category><category>facilitation</category><category>team goals</category><category>quarterly planning</category><author>Dave Clissold</author></item><item><title>How to Create a Product Roadmap: Detail, Timeframes, and Dates</title><link>https://projan.ai/blog/how-to-create-a-product-roadmap-detail-timeframes-and-dates/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-create-a-product-roadmap-detail-timeframes-and-dates/</guid><description>How is the product roadmap created? A practical guide to the inputs, sequencing, how much detail each horizon needs, and whether to commit to dates at all.</description><pubDate>Sat, 29 Aug 2026 00:00:00 GMT</pubDate><category>product roadmap</category><category>roadmap planning</category><category>product management</category><category>prioritisation</category><category>product strategy</category><author>Dave Clissold</author></item><item><title>Requirements Documents Explained: BRD vs FRD vs SRD vs PRD</title><link>https://projan.ai/blog/requirements-documents-explained-brd-vs-frd-vs-srd-vs-prd/</link><guid isPermaLink="true">https://projan.ai/blog/requirements-documents-explained-brd-vs-frd-vs-srd-vs-prd/</guid><description>What is BRD, FRD, and SRD? What each requirements document contains, who signs it, where the acronyms came from, and when a PRD can replace all three.</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate><category>brd</category><category>frd</category><category>srs</category><category>requirements</category><category>business analysis</category><category>product management</category><author>Dave Clissold</author></item><item><title>Definition of Done vs Definition of Ready: Owners, Checklists, and Examples</title><link>https://projan.ai/blog/definition-of-done-vs-definition-of-ready-owners-checklists-and-examples/</link><guid isPermaLink="true">https://projan.ai/blog/definition-of-done-vs-definition-of-ready-owners-checklists-and-examples/</guid><description>What are DoD and DoR in Scrum? A side-by-side comparison, who owns each, what a realistic Definition of Done checklist holds, and how to set it up in Jira.</description><pubDate>Mon, 24 Aug 2026 00:00:00 GMT</pubDate><category>definition of done</category><category>definition of ready</category><category>scrum</category><category>agile quality</category><category>sprint planning</category><category>jira</category><author>Dave Clissold</author></item><item><title>What Steps Should Be Taken When Planning a Meeting?</title><link>https://projan.ai/blog/meeting-planning-and-follow-through-a-complete-playbook-from-agenda-to-action-it/</link><guid isPermaLink="true">https://projan.ai/blog/meeting-planning-and-follow-through-a-complete-playbook-from-agenda-to-action-it/</guid><description>What steps should be taken when planning a meeting? A playbook covering agendas, decision records, action items and what to send in the 24 hours after.</description><pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate><category>meeting planning</category><category>meeting agenda</category><category>action items</category><category>meeting minutes</category><category>meeting follow-up</category><category>decision log</category><author>Dave Clissold</author></item><item><title>Common Project Planning Mistakes and Their Root Causes</title><link>https://projan.ai/blog/common-project-planning-mistakes-and-the-root-causes-behind-them/</link><guid isPermaLink="true">https://projan.ai/blog/common-project-planning-mistakes-and-the-root-causes-behind-them/</guid><description>Common project planning mistakes, traced back to their root causes: unwritten assumptions, single-point estimates, fuzzy scope, and plans nobody replans.</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><category>project planning</category><category>project management</category><category>software delivery</category><category>estimation</category><category>scope</category><category>root cause analysis</category><author>Dave Clissold</author></item><item><title>How to Break Down an Epic Into User Stories</title><link>https://projan.ai/blog/how-to-break-an-epic-into-user-stories-sizing-rules-examples-and-limits/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-break-an-epic-into-user-stories-sizing-rules-examples-and-limits/</guid><description>How to break down an epic into stories: vertical slicing patterns, a worked example, story sizing rules, and how many stories a healthy epic should hold.</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><category>user stories</category><category>epics</category><category>story splitting</category><category>backlog refinement</category><category>agile planning</category><category>sprint planning</category><author>Dave Clissold</author></item><item><title>How to Turn a Business Idea Into an Action Plan</title><link>https://projan.ai/blog/from-idea-to-action-plan-how-to-turn-a-business-idea-into-real-steps/</link><guid isPermaLink="true">https://projan.ai/blog/from-idea-to-action-plan-how-to-turn-a-business-idea-into-real-steps/</guid><description>How to turn an idea into an action plan: run the cheapest test that could prove it wrong, set a stopping rule, then write dated steps with real owners.</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><category>action plan</category><category>business planning</category><category>small business</category><category>idea validation</category><category>product launch</category><author>Dave Clissold</author></item><item><title>Should You Use AI to Write User Stories?</title><link>https://projan.ai/blog/should-you-use-ai-to-write-user-stories/</link><guid isPermaLink="true">https://projan.ai/blog/should-you-use-ai-to-write-user-stories/</guid><description>Should you use AI to write user stories? An honest look at what it drafts well, where it invents context, and how to keep a story worth arguing about.</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><category>user stories</category><category>ai writing</category><category>agile</category><category>backlog</category><category>acceptance criteria</category><category>product management</category><author>Dave Clissold</author></item><item><title>How to Use AI to Write a PRD (and Requirements That Hold Up in Review)</title><link>https://projan.ai/blog/how-to-use-ai-to-write-a-prd-and-requirements-that-hold-up-in-review/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-use-ai-to-write-a-prd-and-requirements-that-hold-up-in-review/</guid><description>How to use AI to create a PRD without shipping fiction: the right workflow, what AI reliably gets wrong, and how to keep requirements honest in review.</description><pubDate>Mon, 17 Aug 2026 00:00:00 GMT</pubDate><category>prd</category><category>ai</category><category>requirements</category><category>product management</category><category>acceptance criteria</category><author>Dave Clissold</author></item><item><title>Running a Client Kick-Off Meeting That Actually Sets Expectations</title><link>https://projan.ai/blog/running-a-client-kick-off-meeting-that-actually-sets-expectations/</link><guid isPermaLink="true">https://projan.ai/blog/running-a-client-kick-off-meeting-that-actually-sets-expectations/</guid><description>What is expected in a kick-off meeting? A consultant&apos;s guide to agreeing scope, access, decision rights and how unwelcome findings should reach the client.</description><pubDate>Mon, 17 Aug 2026 00:00:00 GMT</pubDate><category>consulting</category><category>kick-off meeting</category><category>client expectations</category><category>engagement plan</category><category>stakeholder management</category><author>Dave Clissold</author></item><item><title>How to Plan an API Design and Get It Reviewed</title><link>https://projan.ai/blog/how-to-plan-an-api-design-and-get-it-reviewed-before-you-ship-it/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-plan-an-api-design-and-get-it-reviewed-before-you-ship-it/</guid><description>How to plan an API design: the order to make the decisions in, which parts of it become permanent, and who should review the design before you ship it.</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><category>api design</category><category>design review</category><category>backward compatibility</category><category>versioning</category><category>engineering process</category><author>Dave Clissold</author></item><item><title>What Makes a Good Jira Ticket? Examples and Anti-Patterns</title><link>https://projan.ai/blog/what-makes-a-good-jira-ticket-best-practices-examples-and-anti-patterns/</link><guid isPermaLink="true">https://projan.ai/blog/what-makes-a-good-jira-ticket-best-practices-examples-and-anti-patterns/</guid><description>What makes a good Jira ticket? The fields that matter, titles worth reading, a weak ticket rewritten, what bugs need, and the anti-patterns that cost you.</description><pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate><category>jira</category><category>tickets</category><category>bug reports</category><category>backlog</category><category>agile</category><category>product management</category><author>Dave Clissold</author></item><item><title>How to Write a Summary of Findings Your Client Will Actually Read</title><link>https://projan.ai/blog/how-to-write-a-summary-of-findings-your-client-will-actually-read/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-write-a-summary-of-findings-your-client-will-actually-read/</guid><description>How to write a summary of findings report: what to include, how long it should be, and how to compress a long report without losing the evidence trail.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate><category>summary of findings</category><category>consulting reports</category><category>executive summary</category><category>client reporting</category><category>findings report</category><author>Dave Clissold</author></item><item><title>Brand Messaging Framework: What It Is and How to Write One</title><link>https://projan.ai/blog/brand-messaging-framework-what-it-is-how-to-write-one-and-examples-that-stick/</link><guid isPermaLink="true">https://projan.ai/blog/brand-messaging-framework-what-it-is-how-to-write-one-and-examples-that-stick/</guid><description>What is a brand messaging framework? What goes in one, how to write it step by step, a worked example, and why most frameworks quietly stop being used.</description><pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate><category>brand messaging</category><category>messaging framework</category><category>brand strategy</category><category>product marketing</category><category>positioning</category><author>Dave Clissold</author></item><item><title>What Good Requirements Look Like (and How to Write Them)</title><link>https://projan.ai/blog/what-good-requirements-look-like-and-how-to-write-them/</link><guid isPermaLink="true">https://projan.ai/blog/what-good-requirements-look-like-and-how-to-write-them/</guid><description>What do good requirements look like? Weak and strong versions of the same requirement side by side, plus the testability rule that decides between them.</description><pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate><category>requirements</category><category>requirements writing</category><category>specifications</category><category>non-functional requirements</category><category>product management</category><author>Dave Clissold</author></item><item><title>How to Write a Proper PRD: Structure and Best Practices</title><link>https://projan.ai/blog/how-to-write-a-prd-structure-best-practices-and-mistakes-to-avoid/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-write-a-prd-structure-best-practices-and-mistakes-to-avoid/</guid><description>How to write a proper PRD: the sections it needs, a step-by-step process, how to document assumptions properly, and the mistakes that cause late rework.</description><pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate><category>prd</category><category>product requirements</category><category>product management</category><category>requirements writing</category><category>product documentation</category><author>Dave Clissold</author></item><item><title>Technical Documentation Types: What Agile Software Teams Actually Need to Write</title><link>https://projan.ai/blog/technical-documentation-types-what-agile-software-teams-actually-need-to-write/</link><guid isPermaLink="true">https://projan.ai/blog/technical-documentation-types-what-agile-software-teams-actually-need-to-write/</guid><description>What are the 4 types of technical documentation? The Diataxis answer explained, plus the short list of documents an agile team should actually maintain.</description><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><category>technical documentation</category><category>documentation types</category><category>agile documentation</category><category>rfc</category><category>engineering practices</category><author>Dave Clissold</author></item><item><title>PRD vs Product Spec vs Technical Spec vs Functional Spec: What Each Document Is For</title><link>https://projan.ai/blog/prd-vs-product-spec-vs-technical-spec-vs-functional-spec-what-each-document-is-f/</link><guid isPermaLink="true">https://projan.ai/blog/prd-vs-product-spec-vs-technical-spec-vs-functional-spec-what-each-document-is-f/</guid><description>What is the difference between a PRD and a technical specification? A working guide to PRDs, product specs, technical specs and functional specs at work.</description><pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate><category>prd</category><category>technical spec</category><category>functional spec</category><category>product spec</category><category>requirements</category><category>product management</category><author>Dave Clissold</author></item><item><title>How to Write a Risk Statement: The Three-Part Structure</title><link>https://projan.ai/blog/how-to-write-a-risk-statement-the-three-part-structure-and-what-makes-a-risk-rea/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-write-a-risk-statement-the-three-part-structure-and-what-makes-a-risk-rea/</guid><description>What is the three-part structure used to define a risk statement? Cause, event and consequence, with worked rewrites plus a clear risk versus issue test.</description><pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate><category>risk statement</category><category>risk register</category><category>risk management</category><category>project risk</category><category>raid log</category><author>Dave Clissold</author></item><item><title>What Are the 4 Types of Operational Plans? A Startup View</title><link>https://projan.ai/blog/operational-planning-for-startups-the-4-plan-types-and-the-annual-cycle/</link><guid isPermaLink="true">https://projan.ai/blog/operational-planning-for-startups-the-4-plan-types-and-the-annual-cycle/</guid><description>What are the 4 types of operational plans? The honest answer, the standing versus single-use split that does hold up, and the annual cycle a startup needs.</description><pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate><category>operational planning</category><category>startup operations</category><category>annual planning</category><category>operating plan</category><category>founders</category><author>Dave Clissold</author></item><item><title>Epic vs User Story vs Task: How to Break Work Down Without Losing the Thread</title><link>https://projan.ai/blog/epic-vs-user-story-vs-task-how-to-break-work-down-without-losing-the-thread/</link><guid isPermaLink="true">https://projan.ai/blog/epic-vs-user-story-vs-task-how-to-break-work-down-without-losing-the-thread/</guid><description>What is the difference between an epic, a user story, and a task? Scope, audience, estimation and lifespan compared, plus where Jira muddles the words.</description><pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate><category>epics</category><category>user stories</category><category>backlog</category><category>agile</category><category>jira</category><category>product management</category><author>Dave Clissold</author></item><item><title>What Should Be Included in a Software Test Plan?</title><link>https://projan.ai/blog/how-to-write-a-software-test-plan-structure-steps-and-what-to-include/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-write-a-software-test-plan-structure-steps-and-what-to-include/</guid><description>What should be included in a software test plan? The sections that matter, the steps for writing one, and how much detail is actually worth the effort.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><category>test plan</category><category>software testing</category><category>qa</category><category>test planning</category><category>release management</category><author>Dave Clissold</author></item><item><title>How to Write a PRD in 2026: The Complete Guide for Product Managers</title><link>https://projan.ai/blog/how-to-write-a-prd/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-write-a-prd/</guid><description>Learn how to write a Product Requirements Document (PRD) that developers actually use. Includes templates, examples, and tips from experienced PMs.</description><pubDate>Tue, 10 Mar 2026 00:00:00 GMT</pubDate><category>PRD</category><category>product management</category><category>guide</category><author>Dave Clissold</author></item><item><title>How to Make AI Coding Tools Actually Useful - Part 2</title><link>https://projan.ai/blog/how-to-make-ai-coding-tools-actually-useful/</link><guid isPermaLink="true">https://projan.ai/blog/how-to-make-ai-coding-tools-actually-useful/</guid><description>AI coding agents are only as good as the requirements you give them. Here&apos;s a practical framework for turning vibe coding into structured, reliable development.</description><pubDate>Sun, 08 Mar 2026 00:00:00 GMT</pubDate><category>ai coding</category><category>vibe coding</category><category>product requirements</category><category>ai tools</category><category>developer productivity</category><category>planning</category><category>acceptance criteria</category><author>Dave Clissold</author></item><item><title>AI Coding Tools Are Incredible (Until You Skip the Planning) - Part 1</title><link>https://projan.ai/blog/ai-coding-tools-are-incredible-until-you-skip-planning/</link><guid isPermaLink="true">https://projan.ai/blog/ai-coding-tools-are-incredible-until-you-skip-planning/</guid><description>AI coding agents can build features in minutes. But without clear requirements, they build the wrong features in minutes. Here&apos;s what goes wrong when you vibe code without a plan.</description><pubDate>Thu, 05 Mar 2026 00:00:00 GMT</pubDate><category>ai coding</category><category>vibe coding</category><category>product planning</category><category>ai tools</category><category>edge cases</category><category>requirements</category><category>cursor</category><category>copilot</category><author>Dave Clissold</author></item><item><title>Why Sharing Your Product Roadmap Publicly Builds More Trust Than You&apos;d Expect</title><link>https://projan.ai/blog/transparent-planning-builds-trust/</link><guid isPermaLink="true">https://projan.ai/blog/transparent-planning-builds-trust/</guid><description>Sharing an honest public roadmap builds user trust, improves feedback quality, and creates advocates. Here&apos;s how to do it without handing competitors your playbook.</description><pubDate>Sun, 01 Mar 2026 00:00:00 GMT</pubDate><category>transparency</category><category>build in public</category><category>product roadmap</category><category>startup trust</category><category>community building</category><author>Dave Clissold</author></item><item><title>How Scope Creep Nearly Killed Our Startup</title><link>https://projan.ai/blog/scope-creep-nearly-killed-our-startup/</link><guid isPermaLink="true">https://projan.ai/blog/scope-creep-nearly-killed-our-startup/</guid><description>We said yes to every feature request and built a product that did 20 things badly. Cutting 70% of features saved us. Here&apos;s the full story and how to prevent scope creep.</description><pubDate>Wed, 25 Feb 2026 00:00:00 GMT</pubDate><category>scope creep</category><category>startup failure</category><category>product planning</category><category>startup mistakes</category><category>project management</category><author>Dave Clissold</author></item><item><title>5 Conversations Every SaaS Founder Should Have Before Writing Code</title><link>https://projan.ai/blog/5-conversations-before-writing-code/</link><guid isPermaLink="true">https://projan.ai/blog/5-conversations-before-writing-code/</guid><description>Before building your SaaS, have these 5 critical conversations: potential users, your technical cofounder, someone who failed, a competitor&apos;s customer, and yourself.</description><pubDate>Fri, 20 Feb 2026 00:00:00 GMT</pubDate><category>saas</category><category>pre-development planning</category><category>customer development</category><category>startup validation</category><category>product planning</category><author>Dave Clissold</author></item><item><title>What Investors Actually Look for in Your Technical Roadmap</title><link>https://projan.ai/blog/what-investors-look-for-in-technical-roadmap/</link><guid isPermaLink="true">https://projan.ai/blog/what-investors-look-for-in-technical-roadmap/</guid><description>Investors don&apos;t care about your tech stack. They want milestones tied to business outcomes, clear trade-offs, and a realistic 6-12 month plan. Here&apos;s what to show them.</description><pubDate>Mon, 16 Feb 2026 00:00:00 GMT</pubDate><category>investor pitch</category><category>technical roadmap</category><category>fundraising</category><category>accelerator</category><category>startup planning</category><author>Dave Clissold</author></item><item><title>Shipping AI Features Without a Spec Is Like Flying Without Instruments</title><link>https://projan.ai/blog/shipping-ai-without-spec-flying-without-instruments/</link><guid isPermaLink="true">https://projan.ai/blog/shipping-ai-without-spec-flying-without-instruments/</guid><description>AI features need requirements that traditional specs don&apos;t cover: error rates, fallback behaviors, evaluation criteria. Here&apos;s what an AI feature spec should include.</description><pubDate>Wed, 11 Feb 2026 00:00:00 GMT</pubDate><category>ai product development</category><category>ai requirements</category><category>product planning</category><category>ai features</category><category>technical planning</category><author>Dave Clissold</author></item><item><title>Why Solo Founders Need Requirements More Than Teams Do</title><link>https://projan.ai/blog/why-solo-founders-need-requirements-more/</link><guid isPermaLink="true">https://projan.ai/blog/why-solo-founders-need-requirements-more/</guid><description>Solo founders skip planning because there&apos;s nobody to plan for. That&apos;s exactly why they need it most. Your blind spots ship to production when nobody catches them.</description><pubDate>Fri, 06 Feb 2026 00:00:00 GMT</pubDate><category>solo founder</category><category>product requirements</category><category>indie hacker</category><category>planning</category><category>solo developer</category><author>Dave Clissold</author></item><item><title>Product Managers Are Not Typists: The Documentation Burden Is Real</title><link>https://projan.ai/blog/product-managers-are-not-typists/</link><guid isPermaLink="true">https://projan.ai/blog/product-managers-are-not-typists/</guid><description>PMs spend too much time formatting documents and not enough time thinking. Here&apos;s why treating PRDs as literary works is killing your product team&apos;s velocity.</description><pubDate>Sun, 01 Feb 2026 00:00:00 GMT</pubDate><category>product management</category><category>prd writing</category><category>productivity</category><category>product manager burnout</category><category>documentation</category><author>Dave Clissold</author></item><item><title>The Requirements Template That Reduced Our Client Revisions by 60%</title><link>https://projan.ai/blog/requirements-template-reduced-client-revisions/</link><guid isPermaLink="true">https://projan.ai/blog/requirements-template-reduced-client-revisions/</guid><description>An agency requirements template that cut client revision rounds by 60%. Walk through each section, including the &apos;out of scope&apos; clause that changed everything.</description><pubDate>Tue, 27 Jan 2026 00:00:00 GMT</pubDate><category>requirements template</category><category>client management</category><category>agency efficiency</category><category>project scoping</category><category>client revisions</category><author>Dave Clissold</author></item><item><title>The 10-Minute Planning Session That Keeps My Side Projects Alive</title><link>https://projan.ai/blog/10-minute-planning-session-side-project/</link><guid isPermaLink="true">https://projan.ai/blog/10-minute-planning-session-side-project/</guid><description>A simple 10-minute planning ritual before each coding session that prevents side projects from dying. Five steps to stay focused with limited time.</description><pubDate>Thu, 22 Jan 2026 00:00:00 GMT</pubDate><category>side project planning</category><category>productivity</category><category>weekend projects</category><category>project management</category><category>developer productivity</category><author>Dave Clissold</author></item><item><title>How I Turned My Changelog Into a Growth Channel</title><link>https://projan.ai/blog/how-i-turned-my-changelog-into-a-growth-channel/</link><guid isPermaLink="true">https://projan.ai/blog/how-i-turned-my-changelog-into-a-growth-channel/</guid><description>Writing detailed changelogs drove signups and SEO traffic. Here&apos;s how treating each entry as a mini story turned a boring update log into a marketing asset.</description><pubDate>Sat, 17 Jan 2026 00:00:00 GMT</pubDate><category>changelog</category><category>build in public</category><category>growth</category><category>indie hacker</category><category>content marketing</category><author>Dave Clissold</author></item><item><title>We Wasted 3 Months Building the Wrong Thing</title><link>https://projan.ai/blog/we-wasted-3-months-building-wrong-thing/</link><guid isPermaLink="true">https://projan.ai/blog/we-wasted-3-months-building-wrong-thing/</guid><description>A startup team built for 3 months based on Slack messages and verbal agreements. Here&apos;s what happened when they shipped, and how to avoid the same mistake.</description><pubDate>Tue, 13 Jan 2026 00:00:00 GMT</pubDate><category>startup mistakes</category><category>building wrong product</category><category>product validation</category><category>founder mistakes</category><category>startup planning</category><author>Dave Clissold</author></item><item><title>From University Project to Y Combinator Application</title><link>https://projan.ai/blog/from-university-project-to-yc-application/</link><guid isPermaLink="true">https://projan.ai/blog/from-university-project-to-yc-application/</guid><description>What a student team changed to turn their capstone project into a credible YC application. Academic docs vs startup docs, and why the difference matters.</description><pubDate>Thu, 08 Jan 2026 00:00:00 GMT</pubDate><category>y combinator</category><category>university startup</category><category>student founders</category><category>startup application</category><category>yc application</category><author>Dave Clissold</author></item><item><title>Edge Cases Are Not Edge Cases. They Are the Product.</title><link>https://projan.ai/blog/edge-cases-are-not-edge-cases/</link><guid isPermaLink="true">https://projan.ai/blog/edge-cases-are-not-edge-cases/</guid><description>The &apos;edge cases&apos; discovered during development are usually planning failures. Here&apos;s why PMs should catch them during requirements, not QA.</description><pubDate>Sat, 03 Jan 2026 00:00:00 GMT</pubDate><category>edge cases</category><category>product requirements</category><category>software development</category><category>product management</category><category>qa testing</category><author>Dave Clissold</author></item><item><title>The Spec That Saved Our Series A</title><link>https://projan.ai/blog/the-spec-that-saved-our-series-a/</link><guid isPermaLink="true">https://projan.ai/blog/the-spec-that-saved-our-series-a/</guid><description>A SaaS startup nearly lost their Series A because they couldn&apos;t articulate their roadmap. Here&apos;s how writing it down saved the deal.</description><pubDate>Sat, 27 Dec 2025 00:00:00 GMT</pubDate><category>series a</category><category>fundraising</category><category>product spec</category><category>saas</category><category>startup documentation</category><category>product strategy</category><author>Dave Clissold</author></item><item><title>AI Projects Need Better Requirements, Not Better Models</title><link>https://projan.ai/blog/ai-projects-need-better-requirements-not-models/</link><guid isPermaLink="true">https://projan.ai/blog/ai-projects-need-better-requirements-not-models/</guid><description>Most AI project failures aren&apos;t about the model. They&apos;re about unclear requirements. Here&apos;s how to write requirements for AI features that actually work.</description><pubDate>Sat, 20 Dec 2025 00:00:00 GMT</pubDate><category>ai requirements</category><category>ai product management</category><category>ai development</category><category>product requirements</category><category>ai planning</category><author>Dave Clissold</author></item><item><title>The Documentation Checklist Every Accelerator Team Needs 8 Weeks Before Demo Day</title><link>https://projan.ai/blog/accelerator-documentation-checklist/</link><guid isPermaLink="true">https://projan.ai/blog/accelerator-documentation-checklist/</guid><description>A practical checklist of documentation every startup needs before demo day: product vision, technical architecture, user research, roadmap, and financials.</description><pubDate>Tue, 16 Dec 2025 00:00:00 GMT</pubDate><category>accelerator</category><category>demo day</category><category>startup documentation</category><category>pitch preparation</category><category>technical roadmap</category><author>Dave Clissold</author></item><item><title>Stop Building Features Nobody Asked For</title><link>https://projan.ai/blog/stop-building-features-nobody-asked-for/</link><guid isPermaLink="true">https://projan.ai/blog/stop-building-features-nobody-asked-for/</guid><description>The indie hacker&apos;s biggest trap: building features that are fun instead of features users need. Here&apos;s how to break the cycle.</description><pubDate>Thu, 11 Dec 2025 00:00:00 GMT</pubDate><category>feature creep</category><category>indie hacker</category><category>product development</category><category>user feedback</category><category>building products</category><author>Dave Clissold</author></item><item><title>The Client Said &apos;Build What You Think Is Best.&apos; It Was a Trap.</title><link>https://projan.ai/blog/client-said-build-what-you-think-is-best/</link><guid isPermaLink="true">https://projan.ai/blog/client-said-build-what-you-think-is-best/</guid><description>When a client gives you total creative freedom, it sounds like a dream. Here&apos;s why it&apos;s actually a requirements disaster waiting to happen.</description><pubDate>Sun, 07 Dec 2025 00:00:00 GMT</pubDate><category>client management</category><category>agency work</category><category>requirements gathering</category><category>project management</category><category>client communication</category><author>Dave Clissold</author></item><item><title>Acceptance Criteria Developers Actually Thank You For</title><link>https://projan.ai/blog/acceptance-criteria-developers-thank-you-for/</link><guid isPermaLink="true">https://projan.ai/blog/acceptance-criteria-developers-thank-you-for/</guid><description>Learn how to write acceptance criteria that developers love. 5 real examples of bad AC rewritten as good AC using the Given/When/Then pattern.</description><pubDate>Tue, 02 Dec 2025 00:00:00 GMT</pubDate><category>acceptance criteria</category><category>user stories</category><category>product management</category><category>developer experience</category><category>requirements</category><author>Dave Clissold</author></item><item><title>Your Cofounder Disagrees About the Roadmap. Now What?</title><link>https://projan.ai/blog/your-cofounder-disagrees-about-the-roadmap/</link><guid isPermaLink="true">https://projan.ai/blog/your-cofounder-disagrees-about-the-roadmap/</guid><description>Cofounder roadmap disagreements are normal. Here&apos;s a framework to resolve them without damaging the relationship or stalling your startup.</description><pubDate>Fri, 28 Nov 2025 00:00:00 GMT</pubDate><category>cofounder disagreements</category><category>startup roadmap</category><category>product strategy</category><category>founder conflicts</category><category>startup planning</category><author>Dave Clissold</author></item><item><title>The Weekend Project Trap: Why Most Side Projects Die on Monday</title><link>https://projan.ai/blog/the-weekend-project-trap/</link><guid isPermaLink="true">https://projan.ai/blog/the-weekend-project-trap/</guid><description>Side projects die because of context switching, not motivation. A 10-minute habit at the end of each session can keep your project alive between weekends.</description><pubDate>Mon, 24 Nov 2025 00:00:00 GMT</pubDate><category>side projects</category><category>weekend projects</category><category>productivity</category><category>planning</category><category>developer side projects</category><author>Dave Clissold</author></item><item><title>Building in Public Is Not Free Marketing</title><link>https://projan.ai/blog/building-in-public-is-not-free-marketing/</link><guid isPermaLink="true">https://projan.ai/blog/building-in-public-is-not-free-marketing/</guid><description>Building in public gets romanticized as free marketing. The real value isn&apos;t followers or customers. It&apos;s the planning discipline it forces on you.</description><pubDate>Wed, 19 Nov 2025 00:00:00 GMT</pubDate><category>build in public</category><category>indie hacker</category><category>marketing</category><category>startup marketing</category><category>transparency</category><author>Dave Clissold</author></item><item><title>The One Question That Saves Every PRD</title><link>https://projan.ai/blog/the-one-question-that-saves-every-prd/</link><guid isPermaLink="true">https://projan.ai/blog/the-one-question-that-saves-every-prd/</guid><description>Vague requirements become specific when you ask one question: &apos;How will we know this is done?&apos; Here are real examples of how it transforms PRDs.</description><pubDate>Tue, 11 Nov 2025 00:00:00 GMT</pubDate><category>prd</category><category>product requirements</category><category>acceptance criteria</category><category>product management</category><category>requirements writing</category><author>Dave Clissold</author></item><item><title>What I Wish I Knew Before My First Hackathon</title><link>https://projan.ai/blog/what-i-wish-i-knew-before-my-first-hackathon/</link><guid isPermaLink="true">https://projan.ai/blog/what-i-wish-i-knew-before-my-first-hackathon/</guid><description>The biggest hackathon mistake is jumping straight to code. Winning teams plan first. Here&apos;s practical advice for your first hackathon from someone who&apos;s been on both sides.</description><pubDate>Thu, 06 Nov 2025 00:00:00 GMT</pubDate><category>hackathon</category><category>student developers</category><category>project planning</category><category>team projects</category><category>hackathon tips</category><author>Dave Clissold</author></item><item><title>Planning AI Features When the Tech Changes Every Week</title><link>https://projan.ai/blog/planning-ai-features-when-tech-changes-weekly/</link><guid isPermaLink="true">https://projan.ai/blog/planning-ai-features-when-tech-changes-weekly/</guid><description>AI capabilities shift constantly, but your product requirements don&apos;t have to. Separate the &apos;what&apos; from the &apos;how&apos; to write stable AI feature specs.</description><pubDate>Sat, 01 Nov 2025 00:00:00 GMT</pubDate><category>ai development</category><category>planning</category><category>product requirements</category><category>ai features</category><category>technical planning</category><author>Dave Clissold</author></item><item><title>How We Stopped Losing Money on Fixed-Price Projects</title><link>https://projan.ai/blog/how-we-stopped-losing-money-fixed-price-projects/</link><guid isPermaLink="true">https://projan.ai/blog/how-we-stopped-losing-money-fixed-price-projects/</guid><description>Agencies lose money on fixed-price work because scoping is bad. Here&apos;s how structured requirement gathering transformed our estimates and profitability.</description><pubDate>Mon, 27 Oct 2025 00:00:00 GMT</pubDate><category>agency pricing</category><category>fixed price projects</category><category>client management</category><category>scope creep</category><category>project scoping</category><author>Dave Clissold</author></item><item><title>I Shipped 4 Side Projects Last Year and Finished None of Them</title><link>https://projan.ai/blog/shipped-4-side-projects-finished-none/</link><guid isPermaLink="true">https://projan.ai/blog/shipped-4-side-projects-finished-none/</guid><description>A confession about the side project cycle: start excited, lose steam, abandon, repeat. The fix wasn&apos;t discipline. It was knowing what done looks like.</description><pubDate>Tue, 21 Oct 2025 00:00:00 GMT</pubDate><category>side projects</category><category>indie hacker</category><category>shipping</category><category>productivity</category><category>focus</category><author>Dave Clissold</author></item><item><title>Why Your MVP Takes 6 Months Instead of 6 Weeks</title><link>https://projan.ai/blog/why-your-mvp-takes-6-months/</link><guid isPermaLink="true">https://projan.ai/blog/why-your-mvp-takes-6-months/</guid><description>Most MVPs blow past their timeline because founders skip requirements. Here&apos;s why scope creep happens and how to actually ship a minimum viable product.</description><pubDate>Thu, 16 Oct 2025 00:00:00 GMT</pubDate><category>mvp</category><category>startup planning</category><category>product development</category><category>scope creep</category><category>founders</category><author>Dave Clissold</author></item><item><title>Why Sprint Planning Feels Like Groundhog Day (And How to Break the Cycle)</title><link>https://projan.ai/blog/why-sprint-planning-feels-like-groundhog-day/</link><guid isPermaLink="true">https://projan.ai/blog/why-sprint-planning-feels-like-groundhog-day/</guid><description>Sprint planning keeps repeating the same problems: vague requirements, confused engineers, shifting scope. Here are concrete fixes that actually work.</description><pubDate>Sun, 12 Oct 2025 00:00:00 GMT</pubDate><category>sprint planning</category><category>product management</category><category>agile</category><category>scrum</category><category>team alignment</category><author>Dave Clissold</author></item></channel></rss>