When a Demo Fails (And Why That’s Valuable)
We tested an interactive Jira Software demo to improve signups. While it didn’t increase conversions, it revealed valuable insights that shaped future onboarding experiments.
Product
Jira Software
What I did
Product Design
My role
design lead
Time line
6 weeks
When a Demo Fails (And Why That’s Valuable)
We tested an interactive Jira Software demo to improve signups. While it didn’t increase conversions, it revealed valuable insights that shaped future onboarding experiments.
Product
Jira Software
What I did
Product Design
My role
design lead
Time line
6 weeks
When a Demo Fails (And Why That’s Valuable)
We tested an interactive Jira Software demo to improve signups. While it didn’t increase conversions, it revealed valuable insights that shaped future onboarding experiments.
Product
Jira Software
What I did
Product Design
My role
design lead
Time line
6 weeks
When a Demo Fails (And Why That’s Valuable)
We tested an interactive Jira Software demo to improve signups. While it didn’t increase conversions, it revealed valuable insights that shaped future onboarding experiments.
Product
Jira Software
What I did
Product Design
My role
design lead
Time line
6 weeks
The Why
The Why
Jira Software struggled to communicate its value to new users before signup. Existing tours were static or buried, leading to low engagement and high drop-offs. A previous experiment adding interactivity to feature pages had shown a ~10% uplift in signups and stronger first-week engagement. Building on that success, the team asked: could we design an interactive, hands-on demo that let users try Jira before creating an account?
Jira Software struggled to communicate its value to new users before signup. Existing tours were static or buried, leading to low engagement and high drop-offs. A previous experiment adding interactivity to feature pages had shown a ~10% uplift in signups and stronger first-week engagement. Building on that success, the team asked: could we design an interactive, hands-on demo that let users try Jira before creating an account?
The Why
Jira Software struggled to communicate its value to new users before signup. Existing tours were static or buried, leading to low engagement and high drop-offs. A previous experiment adding interactivity to feature pages had shown a ~10% uplift in signups and stronger first-week engagement. Building on that success, the team asked: could we design an interactive, hands-on demo that let users try Jira before creating an account?
Context & Constraints
Context & Constraints
Audience: Mix of existing and new users (confounded results).
KPIs: Demo starts/completions; downstream: signup/activation.
Constraints: Placement limits; lightweight build for quick test.
Audience: Mix of existing and new users (confounded results).
KPIs: Demo starts/completions; downstream: signup/activation.
Constraints: Placement limits; lightweight build for quick test.
Context & Constraints
Audience: Mix of existing and new users (confounded results).
KPIs: Demo starts/completions; downstream: signup/activation.
Constraints: Placement limits; lightweight build for quick test.
Process Highlights
Process Highlights
Scroll-depth + click tracking to verify low visibility.
Rapid protos for above-the-fold placement and “guided steps” microcopy.
Defined success events (start, complete, CTA click) to connect to signups.
Scroll-depth + click tracking to verify low visibility.
Rapid protos for above-the-fold placement and “guided steps” microcopy.
Defined success events (start, complete, CTA click) to connect to signups.
Process Highlights
Scroll-depth + click tracking to verify low visibility.
Rapid protos for above-the-fold placement and “guided steps” microcopy.
Defined success events (start, complete, CTA click) to connect to signups.
What we learned
What we learned
Analysis revealed our demo underperformed due to audience misalignment and low visibility—next, we’ll refine our targeting and boost demo placement to maximize reach and impact.
Analysis revealed our demo underperformed due to audience misalignment and low visibility—next, we’ll refine our targeting and boost demo placement to maximize reach and impact.
What we learned
Analysis revealed our demo underperformed due to audience misalignment and low visibility—next, we’ll refine our targeting and boost demo placement to maximize reach and impact.
Target Audience:
Challenge: 30% of participants were existing, logged-in users—outside our intended cohort—diluting the results.
Lesson: Future tests will target only “new-to-new” users to ensure relevance and clear impact.
Experiment Visibility:
Challenge: Our demo sat below the fold, so only 37 % of users ever saw it—limiting its impact.
Lesson: Position interactive elements above the fold to ensure they reach and engage the majority of visitors.
Data Dilution:
Challenge: Exposure fired on page load—counting users who never engaged and skewing our metrics.
Lesson: Trigger exposure only after a user interacts with the demo to capture true engagement.
Process
Process
This overview spans initial research through final execution and illustrates how I crafted an engaging interactive demo. The process prioritized user needs and delivered tangible results by leveraging data-driven insights and collaborative workshops.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
This overview spans initial research through final execution and illustrates how I crafted an engaging interactive demo. The process prioritized user needs and delivered tangible results by leveraging data-driven insights and collaborative workshops.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Process
This overview spans initial research through final execution and illustrates how I crafted an engaging interactive demo. The process prioritized user needs and delivered tangible results by leveraging data-driven insights and collaborative workshops.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Data Analysis:
Analyzed A/B testing results and heatmap data from the previous timeline demo to understand user behaviors and drop-off points.
Identified areas for improvement, such as visibility and step completion rates.
Workshops:
Facilitated a Crazy Eights workshop with PMs, engineers, and stakeholders to generate ideas and align on the demo's user flow.
Prioritized simplicity and engagement to maximize impact.
Design and Development:
Built a streamlined version of Jira Software, focused on board and issue features.
Added content-populated guiding cards and interactive elements (editable fields, pre-filled content) to create an engaging, step-by-step demo experience.
Final Design
The final interactive demo allowed users to explore Jira Software’s board and issue features in a hands-on, guided format, seamlessly merging product functionality with marketing for an authentic experience.
Challenges:
Despite strong engagement, the demo did not reach the 5% signup goal.
Key obstacles included targeting a broad audience and the demo’s low-visibility placement.
Final Design
The final interactive demo allowed users to explore Jira Software’s board and issue features in a hands-on, guided format, seamlessly merging product functionality with marketing for an authentic experience.
Challenges:
Despite strong engagement, the demo did not reach the 5% signup goal.
Key obstacles included targeting a broad audience and the demo’s low-visibility placement.
Final Design
The final interactive demo allowed users to explore Jira Software’s board and issue features in a hands-on, guided format, seamlessly merging product functionality with marketing for an authentic experience.
Challenges:
Despite strong engagement, the demo did not reach the 5% signup goal.
Key obstacles included targeting a broad audience and the demo’s low-visibility placement.
Final Design
The final interactive demo allowed users to explore Jira Software’s board and issue features in a hands-on, guided format, seamlessly merging product functionality with marketing for an authentic experience.
Challenges:
Despite strong engagement, the demo did not reach the 5% signup goal.
Key obstacles included targeting a broad audience and the demo’s low-visibility placement.
Reflection
Lessons Learned
Target Audience:
Challenge: The experiment targeted all users visiting the product tour, but 30% were already logged in and not in the target demographic.
Lesson: Narrow the target audience to new users (N2N) for future experiments.
Visibility:
Challenge: The demo was placed below the fold, with only 37% of users scrolling to view it.
Lesson: Ensure interactive elements are visible above the fold to maximize exposure.
Data Dilution:
Challenge: The exposure event fired at page load, including users who never interacted with the demo.
Lesson: Redefine exposure criteria to reflect actual interaction.
Reflection
Lessons Learned
Target Audience:
Challenge: The experiment targeted all users visiting the product tour, but 30% were already logged in and not in the target demographic.
Lesson: Narrow the target audience to new users (N2N) for future experiments.
Visibility:
Challenge: The demo was placed below the fold, with only 37% of users scrolling to view it.
Lesson: Ensure interactive elements are visible above the fold to maximize exposure.
Data Dilution:
Challenge: The exposure event fired at page load, including users who never interacted with the demo.
Lesson: Redefine exposure criteria to reflect actual interaction.
Reflection
Lessons Learned
Target Audience:
Challenge: The experiment targeted all users visiting the product tour, but 30% were already logged in and not in the target demographic.
Lesson: Narrow the target audience to new users (N2N) for future experiments.
Visibility:
Challenge: The demo was placed below the fold, with only 37% of users scrolling to view it.
Lesson: Ensure interactive elements are visible above the fold to maximize exposure.
Data Dilution:
Challenge: The exposure event fired at page load, including users who never interacted with the demo.
Lesson: Redefine exposure criteria to reflect actual interaction.
Reflection
Lessons Learned
Target Audience:
Challenge: The experiment targeted all users visiting the product tour, but 30% were already logged in and not in the target demographic.
Lesson: Narrow the target audience to new users (N2N) for future experiments.
Visibility:
Challenge: The demo was placed below the fold, with only 37% of users scrolling to view it.
Lesson: Ensure interactive elements are visible above the fold to maximize exposure.
Data Dilution:
Challenge: The exposure event fired at page load, including users who never interacted with the demo.
Lesson: Redefine exposure criteria to reflect actual interaction.
More Works More Works
More Works More Works
bildkritik
Go Back To Top
bildkritik
Go Back To Top