Planning Jtbd

JTBD RUBRIC Use this template to define the real job users hire your product to do. Each section forces you to look at the struggle, not the solution.

---

The Job

What progress is the user trying to make at this moment State it as a change in their life, not as a feature request.

Format: "When I am [situation], I want to [progress], so I can [desired outcome]."

DesignSetGo's Primary Job

"When I'm building a WordPress site, I want to add professional design features without fighting complex tools, so I can deliver quality work faster and move on to the next project."

Secondary Jobs:

• "When I see a design in my head, I want to build it in WordPress without limitations, so I can match my vision."
• "When I need a form or interactive element, I want it to just work, so I don't waste time troubleshooting."
• "When I use WordPress blocks, I want them to do more, so I don't need to install five different plugins."

---

The Struggle Moment

What triggers the switch Describe the real pain or friction that pushes the user to seek a new solution.

DesignSetGo User Struggles

Developer/Designer:

• "Elementor and Divi feel heavy and break when WordPress updates."
• "I know what I want to build but WordPress blocks can't do it."
• "I'm installing 10 plugins just to get basic features like forms and tabs."
• "Page builders lock me into their ecosystem - if I switch, I lose everything."

Agency/Freelancer:

• "Every page builder has a learning curve - I don't have time to learn another one."
• "My clients need to update their sites but page builders are too complex for them."
• "Sites feel slow and bloated, clients complain about performance."

Site Owner:

• "I want my site to look modern but I don't know how to code."
• "The Block Editor feels limiting compared to what I see on other sites."
• "I need a contact form but I don't want another subscription plugin."

---

Forces of Progress

Identify the four forces that shape the user's choice. Fill in each one with simple language.

Push of the Problem

What frustrates the user today

• Current page builders are bloated and slow my site down
• I need 5-10 plugins to get the features I want
• Page builders break with WordPress updates
• Learning curve is steep for complex tools
• I'm locked into an ecosystem - can't leave without losing content
• My editor looks nothing like the frontend
• Plugins conflict with each other
• I'm paying monthly subscriptions just for basic features

Pull of the New Solution

What about DesignSetGo feels attractive

• Works exactly like WordPress - if you know blocks, you know this
• 43 blocks + 11 extensions in one lightweight plugin (no subscriptions)
• Extensions enhance ANY block (even core WordPress blocks)
• Built with WordPress standards - won't break on updates
• Performance-focused - no bloat, no slow load times
• What you see in the editor is what you get on the frontend
• Complete form system with no external services
• One plugin replaces multiple plugins

Anxiety of Change

What worries them about trying or switching

• "Will this work with my theme?"
• "Is this just another page builder I have to learn?"
• "What if I install it and it breaks my site?"
• "Will it slow down my site?"
• "What happens when I update WordPress?"
• "Can I remove it later without losing my content?"
• "Is there enough documentation?"

Habit of the Present

What keeps them doing things the old way

• "I already know Elementor/Divi, even if it's frustrating"
• "I've built sites this way for years"
• "My clients expect the [current tool] interface"
• "I have templates in my current page builder"
• "Switching means learning something new"
• "I'm used to the quirks and workarounds"
• "What if the Block Editor doesn't have enough features?"

This section guides design and messaging.

---

The Required Outcomes

What must be true for the user to feel progress These are not features. These are states the user wants to reach.

DesignSetGo Required Outcomes

• "I see my design come to life immediately without refresh delays"
• "I feel confident making changes without breaking my site"
• "My site loads fast and doesn't feel bloated"
• "I can hand off the site to my client and they can update it"
• "I don't need to learn a new system - it feels like WordPress"
• "My blocks work with any theme, including FSE themes"
• "I can remove the plugin later if needed without losing content structure"
• "I get forms, layouts, and interactions without multiple plugins"
• "Updates don't break my site"
• "I stay in control - no black boxes or mysterious output"

---

Barriers to Progress

What gets in the way of making the switch List real blockers. Keep them honest.

DesignSetGo Barriers

Discovery Barriers:

• "I've never heard of this plugin"
• "It's not in the mainstream page builder conversation"
• "No big YouTuber has covered it yet"

Trust Barriers:

• "Is this actively maintained?"
• "What if the developer abandons it?"
• "Only 1.0.0 - is it stable enough for client work?"
• "Not enough reviews/installs to validate quality"

Time Barriers:

• "I don't have time to test yet another tool"
• "Learning curve - even if small - is still time"
• "I'd need to rebuild my templates"

Technical Barriers:

• "Will it work with my specific theme/plugins?"
• "What's the performance impact?"
• "Can I customize it if needed?"

Migration Barriers:

• "I have 50 sites on [current tool]"
• "Converting existing sites seems overwhelming"
• "What about my existing content?"

---

JTBD Scorecard

Rate the experience on how well it delivers progress. Use a simple scale: Strong, Medium, Weak.

DesignSetGo Current State

Progress Factor	Rating	Evidence
Does the user see progress fast?	Strong	Real-time preview, no refresh delays, built with WordPress patterns users already know
Does the user feel safe?	Strong	Built with WP standards, proper deprecation system, editor/frontend parity means no surprises
Does the user stay in control?	Strong	No proprietary markup, clean output, can inspect/customize everything, transparent CSS
Does the product remove friction?	Strong	One plugin replaces many, works like native WordPress, 43 blocks + 11 extensions in one place
Does the product reduce anxiety?	Medium	Technical quality is strong BUT trust barriers exist (new plugin, no big community yet)
Does the product help them continue the job later?	Strong	Native blocks = future-proof, FSE compatible, can remove plugin without losing structure
Does the user return because they see more progress?	Medium	Core functionality complete BUT lacks patterns, templates, and discovery features that drive repeat engagement

Weak Areas = Next Opportunities

Medium: Reduce Anxiety

• Need social proof (reviews, case studies, showcases)
• Documentation/video tutorials for common use cases
• "Trusted by X sites" metrics
• Showcase of real sites built with DesignSetGo

Medium: Return Engagement

• Block patterns library
• Pre-made templates
• Community showcase
• Regular feature announcements
• Newsletter with design tips

---

Progress Moments

List the key moments where the user feels movement. Focus on the first moments and the return moments.

DesignSetGo Progress Moments

First 5 Minutes:

1. Install + Activate - "It's installed, no setup wizard, just works"
2. First Block Insert - "Oh, these are just in the block inserter like native blocks"
3. First Control Change - "The preview updated instantly, just like WordPress blocks"
4. First Extension Discovery - "Wait, I can add animations to ANY block? Even core blocks?"
5. First Form Submission - "I got the email, it just worked, no API keys needed"

First Week: 6. First Client Handoff - "My client can actually use this, it's not overwhelming" 7. First Theme Switch - "I changed themes and nothing broke" 8. First Complex Layout - "I built a landing page without code or a page builder" 9. First Performance Check - "PageSpeed score stayed high even with interactive features" 10. First 'Aha' Moment - "This is what WordPress blocks should have been from the start"

Return Moments: 11. Coming back to edit - "I remember how to use this, it's just WordPress" 12. Building second site - "I'm way faster now, I know which blocks to reach for" 13. Solving new challenge - "I need tabs... oh right, DesignSetGo has that" 14. Recommending to others - "This replaced 5 plugins on my stack"

Amplification Opportunities:

• Onboarding tour highlighting extension power
• "Built with DesignSetGo" showcase
• Quick-start video series
• Template/pattern library for common layouts
• Performance badge ("Built fast, stays fast")

---

Anti-Jobs

What not to build List things users do not hire your product to do.

This keeps scope clean.

What Users DON'T Hire DesignSetGo For

Not a Page Builder Replacement (in the traditional sense):

• Users don't hire DesignSetGo to get a drag-and-drop visual builder separate from WordPress
• Users don't hire DesignSetGo to build a completely different editing experience
• Users don't hire DesignSetGo to learn a proprietary system

Not Site Management:

• Users don't hire DesignSetGo to manage hosting, domains, or servers
• Users don't hire DesignSetGo to handle backups or security
• Users don't hire DesignSetGo to optimize databases or manage updates

Not Complete Design Automation:

• Users don't hire DesignSetGo to automatically design their entire site
• Users don't hire DesignSetGo to replace their design skills
• Users don't hire DesignSetGo to make design decisions for them

Not Theme Framework:

• Users don't hire DesignSetGo to replace their theme
• Users don't hire DesignSetGo to handle site-wide styling (that's theme.json)
• Users don't hire DesignSetGo to manage site templates (that's FSE)

Not eCommerce Solution:

• Users don't hire DesignSetGo to replace WooCommerce
• Users don't hire DesignSetGo to handle payments or inventory
• Users don't hire DesignSetGo to build online stores (though it can style them)

Not Content Management:

• Users don't hire DesignSetGo to manage blog posts, pages, or media
• Users don't hire DesignSetGo to handle SEO or analytics
• Users don't hire DesignSetGo to create or schedule content

Scope Discipline:

• Stay focused on blocks and extensions that enhance the native WordPress experience
• Don't build features that WordPress core or popular plugins already handle well
• Don't create lock-in - always maintain portability and standards compliance
• Don't reinvent WordPress - extend and enhance it

---

How the Job Shapes the Roadmap

Turn the job into product direction. Define what the product must improve next.

This is where JTBD becomes strategy.

Immediate Priorities (Remove Anxiety Barriers)

1. Build Trust & Social Proof

• Get first 100 reviews on WordPress.org
• Create showcase site with real examples
• Document case studies showing real sites built with DesignSetGo
• Video tutorials for each block category
• "How I Replaced Elementor" migration guide

2. Reduce Time-to-Value

• Ship 20+ block patterns for common layouts (hero sections, pricing tables, feature grids)
• Quick-start templates (landing page, about page, services page)
• Interactive onboarding tour highlighting extension power
• Cheat sheet PDF for developers

3. Prove Performance

• Performance comparison benchmarks (vs Elementor/Divi/Kadence)
• "Performance badge" for sites using DesignSetGo
• Lighthouse score showcase
• Core Web Vitals documentation

Medium-term (Increase Return Engagement)

4. Pattern Library Ecosystem

• 50+ professional patterns across all categories
• Community pattern submissions
• Pattern categories (hero, CTA, testimonials, team, pricing, FAQ)
• One-click pattern import

5. Developer Experience

• Custom block scaffolding tools
• Extension development guide
• Hooks and filters documentation
• Child block creation guide

6. Community Building

• Discord/Slack community
• Weekly design challenges
• User showcase gallery
• DesignSetGo site badge/credit system

Long-term (Strengthen Market Position)

7. Pro Features (Without Breaking Core Promise)

• Advanced animation timeline
• Dynamic content blocks (posts, users, custom fields)
• WooCommerce-specific styling blocks
• Advanced form features (multi-step, conditional logic)
• Keep extension system free - charge for advanced implementations

8. Ecosystem Integration

• Verified theme compatibility list
• Popular plugin integrations (ACF, Toolset, etc.)
• Import/export between sites
• AI-assisted pattern generation (trend: not anti-job)

9. Enterprise Features

• Multi-site management
• Role-based block access
• White label options
• Client-safe mode (disable certain features)

What We WON'T Build (Staying True to the Job)

❌ Separate visual builder interface ❌ Proprietary page templates that lock users in ❌ Non-standard output that breaks without the plugin ❌ Heavy frameworks that slow sites down ❌ Monthly subscription for basic features ❌ Features that already exist in WordPress core ❌ "Magic" AI that removes user control

Success Metrics

Measure progress toward the job:

• Time from install to first published page
• Number of plugins replaced per install
• Performance score delta (before/after)
• Client handoff satisfaction
• Theme compatibility rate
• WordPress update survival rate
• User retention after 30/90 days
• "Replaced [page builder]" conversion rate

The North Star

"Make building professional WordPress sites feel as natural as using WordPress itself, but with the power users expect from page builders - without the bloat, lock-in, or learning curve."

Every feature decision should pass this test:

1. Does it make progress faster?
2. Does it reduce anxiety?
3. Does it maintain control?
4. Is it WordPress-native?
5. Could we remove it tomorrow without breaking sites?

If the answer to #5 is "no" - reconsider the approach.

---

Feature Roadmap by Horizon

This section translates the JTBD framework into concrete features organized by development horizons. Each horizon focuses on a specific user outcome and ties directly back to the jobs users hire DesignSetGo to do.

HORIZON 1 (NEXT 1–2 RELEASES)

Theme: "Time-to-value and plugin replacement"

Goal: Help users feel progress in the first week. Reduce the number of separate plugins they need for basic marketing sites.

Target Versions: v1.1–v1.3

A. Layout and Content Structure

Card Block

• Role: Reusable unit for pricing, features, services, and team members
• Why: Every marketing page needs "cards." Designers see this in their head but hit the layout wall with core blocks
• JTBD Link: "Add professional design features without fighting complex tools"

Details:

• Image, title, subtitle, body, CTA, badge
• Layout presets for image top, left, or no image
• Ties into Grid / Row blocks so users drop "Card" into existing layout tools

Card Group Preset Support (enhancement, not a new block)

• Role: Use existing Grid / Row blocks plus "Card" to build full sections fast
• Section presets for 2, 3, 4 cards
• Gap, alignment, and equal height controls tuned for this use

Outcome: "First complex layout" and "first landing page" feel much faster to build.

B. Conversion and Trust Blocks

Testimonial Block

• Role: Replace separate testimonial plugins
• Features:
  • Avatar or image, name, role, company, quote
  • Rating option that stays presentational, not a review system
  • Works inside Slider for "testimonial carousel" pattern

Pricing Table Block

• Role: Replace common pricing table plugins
• Features:
  • Columns for plans, with labels for "Most popular" etc.
  • Plan name, price, period, feature list, CTA
  • Built on Card or Grid internals for consistency

FAQ Block Preset (Accordion enhancement)

• Role: Turn existing Accordion into a "FAQ mode" with better defaults
• Features:
  • Question / answer schema-friendly markup where possible
  • Toggle to show first item open
  • FAQ pattern that site owners drop on pages without extra thinking

Outcome: Users move from "I need 5 plugins" to "DesignSetGo covers testimonials, pricing, FAQ, and layout" for basic sites.

C. Interaction and Motion

Modal / Popup Block

• Role: Replace lightweight modal plugins while staying in content scope
• Features:
  • Trigger options: button, link, or time / scroll percentage
  • Works with any blocks inside
  • Performance-first, no extra framework

Guardrail: No site-wide popup manager. Keep it content-level. Users add it to a page like any other block.

D. Forms: Polish and Trust

Form Presets

• Role: Reduce setup time for common forms
• Features:
  • Ready combinations inside Form Builder for Contact, Lead capture, Newsletter
  • Opinionated spacing and layout presets that match Section / Row

Form Success Message Block (or visual state)

• Role: Make "First form submission" feel polished
• Features:
  • Clear success state above the fold
  • Option to show summary of submitted values for reassurance

Success Signals for Horizon 1

• Fewer "I still need plugin X" comments
• Shorter time from install to first full marketing page
• More "replaced [plugin type]" stories in reviews and docs

---

HORIZON 2 (3–6 MONTHS)

Theme: "Return engagement and patterns built on blocks"

Goal: Use blocks as building units for patterns and quicker site builds, without drifting into full theme or page-builder territory.

Target Versions: v1.4–v1.8

A. Pattern-Friendly "Section" Blocks

These stay as blocks but ship with pattern-first intent.

Hero Section Presets (Section + Row + Card + Button)

• Role: Give users reliable hero layouts
• Features:
  • Text left / image right, centered, split with background overlay
  • Smooth entry animations preconfigured through existing animation extension

Feature List Block

• Role: Compact middle ground between Icon List and full Card
• Features:
  • Icon, heading, short body
  • Vertical or horizontal mode
  • Optimized for "Three features under a hero" sections

Process / Steps Block

• Role: Replace "how it works" plugins
• Features:
  • Numbered steps with title and text
  • Horizontal and vertical layouts
  • Optional connector lines for timeline style

Note: All of these rely on existing container and visual primitives, so maintenance stays low.

B. "Second Site" and Agency Helper Blocks

Section Header Block

• Role: Consistent headings across sections and pages
• Features:
  • Eyebrow text, main heading, optional description, alignment controls
  • Opinionated spacing so sections align across the page

Layout Presets for Common Pages (pattern packs, not new block types)

• Role: Drive return use
• Includes:
  • About page pattern collection built from existing blocks
  • Services page pattern collection
  • Contact page pattern with form, FAQs, and map placeholder

Note: These live as pattern sets, but the roadmap here highlights the block readiness and presets those patterns depend on.

C. "Safe Motion" and UX Polish

Scroll-Linked Sections (enhancement to Scroll Accordion / reveal)

• Role: Give users more control over progressive reveal
• Features:
  • Section intros that show as users scroll
  • Opinionated defaults that still respect performance

Success Signals for Horizon 2

• More repeat usage on second and third sites
• Higher retention after 30 and 90 days
• Users talk about "I know which DesignSetGo blocks to reach for" in feedback

---

HORIZON 3 (6–12 MONTHS)

Theme: "Pro features that respect the anti-jobs"

Goal: Serve power users and agencies with advanced blocks, while staying WordPress-native and within your scope.

Target Versions: v2.x

A. Dynamic Content Blocks

Query Card Block (Pro tier)

• Role: Styled presentation for posts, CPTs, users without replacing core Query Loop
• Features:
  • Works as an inner block template inside Query Loop
  • Hooks into ACF and custom fields for meta display
  • No custom query builder UI, rely on core controls

Dynamic List Block

• Role: Lightweight list of posts or CPTs with tight layout control
• Features:
  • Use core query APIs under the hood
  • Focus on presentation and spacing

B. WooCommerce Styling Helpers

Product Info Block Group (Pro tier)

• Role: Presentation layer on product pages
• Features:
  • Styled title, price, badges, and icon lists inside existing WooCommerce templates
  • No checkout, inventory, or store logic

Product Highlights Block

• Role: Callout sections on product and landing pages
• Features:
  • Built from Card and Icon blocks

C. Advanced Forms

Multi-Step Form Block

• Role: Replace external multi-step form plugins for marketing flows
• Features:
  • Split existing fields into steps
  • Progress indicator at the top
  • Keeps submission on your current AJAX engine

Conditional Fields (Pro feature on top of current fields)

• Role: Simple visibility rules
• Features:
  • Show field based on previous selection
  • Defined through plain controls in the inspector

D. Enterprise and Agency Safety

These stay light and respect "not a management tool."

Client-Safe Mode Toggle (extension)

• Role: Hide advanced controls from clients
• Features:
  • Inspector sections for advanced settings behind a "Pro controls" toggle restricted by role
  • Focus on form, animation, custom CSS, and motion features

Success Signals for Horizon 3

• More "replaced [page builder] on client sites" stories
• Higher usage on WooCommerce and CPT-heavy sites
• Agencies reporting lower plugin counts per build

---

Release Mapping

This section maps the horizons to specific version releases with clear targets.

Version 1.1–1.3 (Horizon 1)

Blocks:

• Card
• Testimonial
• Pricing Table
• FAQ preset
• Basic form presets
• Modal

Target: Reduce plugin count for basic marketing sites and improve first-week progress.

Version 1.4–1.8 (Horizon 2)

Blocks:

• Feature List
• Process / Steps
• Section Header
• Hero and page patterns
• Scroll UX polish

Target: Better second-site experience and higher return engagement.

Version 2.x (Horizon 3)

Blocks:

• Dynamic content presentation blocks
• WooCommerce styling helpers
• Multi-step and conditional forms
• Client-safe controls

Target: Agencies who want to drop Elementor or Divi on new builds while staying WordPress-native.

---

Next Steps

The next step is creating a shorter "internal roadmap" table that maps each block to:

• User story
• Plugin types it replaces
• Success metric

This can be shared with engineering and marketing without the full JTBD text.

---

Auto-generated from docs/planning/JTBD.md. To update, edit the source file and changes will sync on next push to main.