Now let me read the transcript.Good transcript to work with. Let me run it through the full SIGNAL rubric now.
---
**Total Score:** 17/30 — Functional
**Call Pattern:** Strong Signal Grounding, Soft Decision Locking
The first half of this call is a well-structured research readout anchored in real behavioral data — Morgan and Eric walk through Buddy Bar Mobile findings with specific signal evidence, and the team lands on a credible V3 recommendation. The second half shifts into Sean's strategic vision deck, which is generative and high-value but doesn't convert into committed decisions. The call closes with good energy and no confirmed next steps.
**SIGNAL Flow:** Surface and Ground perform above average thanks to concrete test data driving the conversation. Identify and Navigate stay soft — goals are mostly implied and recommendations are offered without formal agreement. Align and Lock are the weakest letters; the call ends without owners, timelines, or restated impact.
**What Went Well**
- Research signals directly shaped the V3 recommendation
- Sean's vision presentation elevated the strategic frame beyond UI decisions
- Reframe adoption was high — the group built on each other's thinking consistently
**Areas for Improvement**
- No success criteria defined for what the V3 test needs to demonstrate
- Polymorphic concepts reviewed without decisions or owners attached
- Call ended without locking next steps, timelines, or a stated business outcome
**Primary Improvement:** Before the next call ends, name one specific owner and date for V3 design — the most concrete output that came out of this meeting.
---
## S — Surface Challenges (3/5)
Morgan does solid problem articulation in the Buddy Bar section — random clicks, missing affordances on mobile, the two-click failure point — and the team moves clearly beyond the stated feature request to the underlying behavior problem. Where Surface falls short is consequence: the cost of inaction stays implicit. We hear what users are doing wrong but not what it's costing in conversion or revenue terms. The Polymorphic section doesn't surface a tension at all — it's a concept walkthrough without a named problem driving it.
### Key Observations
**1. Real user behavior contradicts design assumptions**
> "A lot of participants are clicking randomly on the page to bring up their initial edit actions. And so we want to account for the fact that they may click somewhere where there's not a very clear hit spot."
— Morgan McGowan
>
**2. Two-click failure identified as a specific friction point**
> "When we introduced a second click to open up edit options, we saw sentiment fall down for variation 1, we saw a likelihood of being successful clicking on that plus CTA fall down."
— Morgan McGowan
>
**3. Product philosophy tension surfaced organically**
> "You can't really enjoy the full breadth of what Zazzle has to offer unless you customize something. It's sort of like, no, you gotta do something before you interact or complete the transaction."
— Sean Narvasa
>
### Why this isn't a 5
- No conversion or revenue consequence attached to the friction being described — "users click randomly" is a UX observation, not a quantified business problem
- Polymorphic section never surfaces a named challenge — concepts are presented for reaction, not to solve a defined tension
---
## I — Identify Outcomes (3/5)
The Buddy Bar section has an implicit goal — improve first-click discoverability of edit tools — but it's never stated as a measurable success criterion. Morgan's data presentation implies what "better" looks like, but the team never says "the V3 test succeeds if task completion hits X%." The Polymorphic section is more exploratory still: multiple flows are shown and reacted to, but the question "what does winning look like here?" is never asked or answered. Sean's vision deck comes closest to defining outcomes, but at the strategic level rather than for the specific work being reviewed.
### Key Observations
**1. Task-level goal is clear but not formalized**
> "The specific goal here is change the color of the name on this card."
— Morgan McGowan
>
**2. Business goal is stated directionally but not measured**
> "A lot of these paradigms that we know — and where we're going seems to be much different land, right? It's sort of like content first, mobile first, platform, not e-commerce."
— Sean Narvasa
>
**3. Review criteria for polymorphic options are undefined**
> "Lots, lots to explore here. Curious, Sean, how this aligns to your conception of this Sticky Panda mobile implementation?"
— Eric Zwierzynski
>
### Why this isn't a 5
- No measurable success criteria set for V3 before the call ends — direction agreed, test design not scoped
- Polymorphic concepts reviewed as visual concepts rather than hypotheses with defined outcomes
- "Refine these ideas for testing next week" (Eric) acknowledges future testing without specifying what would constitute a pass
---
## G — Ground in Signals (4/5)
This is the call's strongest dimension. Morgan arrives with specific behavioral data — task success by variation, sentiment scores, first-click distribution — and uses it to make a concrete recommendation. The V3 Frankenstein direction is directly grounded in signal evidence: V2's interaction model outperformed on sentiment, V1's labeled CTAs outperformed on task success. Eric's summary of next steps directly traces back to what the data showed. The signal also lands in the broader conversation — Eric's 4% event platform adoption stat is used to motivate the digital placement debate.
### Key Observations
**1. Signal data drives a specific design recommendation**
> "The real recommendation is actually to create a new variation of this, a variation 3, that's kind of a nice little Frankenstein baby between V1 and V2 — bringing in some of those elements."
— Morgan McGowan
>
**2. Quantified behavior anchors the 'It's Ready' CTA discussion**
> "Add to cart only got 2% of clicks. Personalize got like 40%, so they're right next to each other, but obviously, even in the current iteration, people are like, oh, I personalize first, I'm not gonna go directly to cart."
— Morgan McGowan
>
**3. Low signal baseline for the digital placement decision**
> "We're seeing 4% adoption of the event platform with digital downloads today. So it'd be interesting to see what happens when we make that event option so much more apparent in that digital checkout."
— Eric Zwierzynski
>
### Why this isn't a 5
- The Polymorphic half of the call has no signal grounding — variations are reviewed aesthetically and conceptually, not against data
- Sentiment scores and success rates are referenced directionally but not shared as specific numbers, reducing their anchoring power for decisions
---
## N — Navigate Decisions (3/5)
Morgan leads the Navigate moment in the first half: a clear point of view (V3 = V2 interactions + V1 labeled CTAs), a specific rationale, and Sean's affirmation. That's a solid recommendation landing. The second half is much softer — Eric repeatedly asks Sean how concepts "sit" with him, which invites reaction but avoids leading to a decision. The "digital as gift shop" conversation is valuable thinking but ends without a direction. Sean's vision presentation generates enthusiasm but no formal commitments are extracted from it.
### Key Observations
**1. Research recommendation is crisp and directional**
> "So, ideally, we're going to take the interaction of V2 and some of the iconography, because actually V2 was like the highest performing sentiment as well. The labeled CTAs of V1 were the most performant here. So some type of combination of those two should be our V3."
— Morgan McGowan
>
**2. Design exploration stays open-ended rather than converging**
> "All right, so, Sean, I'm curious how this sits with your thought process."
— Eric Zwierzynski
>
**3. Soft direction without decision on digital placement**
> "I would hope it would be as frictionless as that, but I feel like putting the digital option further upstream — it's almost kind of like some of the thing that we had with the instant downloads."
— Sean Narvasa
>
### Why this isn't a 5
- V3 recommendation is clear for Buddy Bar but wasn't confirmed with an explicit "we're doing this" close
- Polymorphic concepts end with observation, not selection — no option was chosen or deprioritized
- Eric's facilitation style during the Polymorphic section invites input over driving decisions
---
## A — Align Ownership (2/5)
Ownership is diffuse throughout. When Eric asks about status of bets, Sean's answer is "not really… probably scattered across various Jira tickets." For the Buddy Bar work, the V3 design is the obvious next step but no one is named as the person who will build it. Sean mentions Tony for some bets, Karina for detail work, but in the context of future work rather than actions out of this call. Eric offers to support productionization but it's framed as something to "discuss." The structural ownership ambiguity Sean describes ("I would be on the hook for the vast majority") is surfaced but not resolved.
### Key Observations
**1. Status of bets acknowledged as undocumented**
> "Not really. I think it's probably scattered across various Jira tickets. If we wanted to, I could put together a table, in a row, and like, each row has a status and various owners. That's probably like a way to project manage this thing."
— Sean Narvasa
>
**2. Design-to-production handoff discussed but not assigned**
> "Would love to discuss what that potentially looks like. Most of our mocks, where possible, we're using the components from the style guide, and potentially even build out a separate production file that makes it really easy for Jira ticketing and things like that."
— Eric Zwierzynski
>
### Why this is a 2
- No specific owner named for V3 design, the call's primary design output
- Polymorphic next moves are unassigned
- Sean's bet structure exists but owners and statuses aren't confirmed in the room — acknowledged as a gap but not addressed
---
## L — Lock Momentum (2/5)
The call ends warmly but loosely. Eric's "refine these ideas for testing next week" is the closest thing to a next step, but it has no owner or specificity. Sean says he'll send out the deck. No one restates what was decided, what's happening by when, or who's doing it. The call generated significant thinking — V3 direction, gift-shop digital treatment, mobile roadmap priorities — but none of it is confirmed as committed action. The Apple/Mac story Sean uses is compelling framing, but also signals the work of alignment still ahead.
### Key Observations
**1. High-level timeline stated but not committed**
> "I think the goal is to finish all this stuff by September. That would be my hope."
— Sean Narvasa
>
**2. Closing that recaps energy but not decisions**
> "Thanks for the ideas, excited to refine these ideas for testing next week. We'll see you Wednesday."
— Eric Zwierzynski
>
### Why this is a 2
- No restated business impact at close
- No explicit next step with owner and date for V3 design
- Polymorphic directions end as open questions
- "Refine these ideas for testing next week" is a category, not an action
---
## Behavioral Metrics
### Talk Time Ratio
- Eric Zwierzynski (team): ~22% — facilitator + presenter
- Morgan McGowan (team): ~18% — primary research presenter
- Bryan Zmijewski (team): ~5% — light facilitation
- Sean Narvasa (client): ~47% — research reactor + vision presenter
- Jeff (client): ~8% — executive commentary, early drop
### Problem Ownership (client/stakeholder only)
- Count: 8 instances
- Level: **High**
- Examples:
- "We don't think mobile first, so when we do feature development, it tends to be from a desktop first realm."
- "We have done basically zero in terms of mobile product development in the last couple years."
- "The current product page was a product of 30 A-B tests that we ran in 2021 — it was more of just a ping-ponging set of A-B tests."
- Interpretation: Sean is unusually candid about historical platform debt and strategic missteps. Jeff adds to this with his "Frankenstein" characterization of the product page. This level of ownership is an asset — it creates permission for significant change — but it also dominates the conversation, shifting the call from a design review to a strategy session.
### Decision Language (client/stakeholder only)
- Count: 6 instances
- Tone: **Collaborative, aspirational**
- Examples:
- "Let's prioritize customization first."
- "I could see this coming to fruition in the next month or so."
- "I'll send this out."
- Interpretation: Sean's decision language is mostly future-oriented and conditional rather than confirmatory. He describes direction he wants to move in but stops short of committing to specific actions in the room. This creates alignment on vision but leaves execution undefined.
### Reframe Adoption
- Team Reframes: 6
- Client Adoptions: 5
- Adoption Rate: ~83%
- Reframes:
- ✓ Morgan: "Users need edit options on first click, not two-click access" — Sean adopted and extended ("reduce UI further to optimize for first interaction")
- ✓ Morgan: "V3 combines V2 interactions + V1 labeled CTAs" — Sean affirmed ("Nice")
- ✓ Eric: "Labeling is the key differentiator for pickup speed" — Sean aligned
- ✓ Sean: "Product page is a traffic director / billboard" — Jeff adopted enthusiastically
- ✓ Bryan: "The arc is creative confidence" — Sean adopted
- ✗ Eric: "Maybe a toggle progression rather than primary/secondary CTA" — Sean replied "yeah" but it wasn't developed or confirmed
- Interpretation: Reframe adoption is high and mutual — both the team and Sean are generating reframes that the room builds on. This reflects a collaborative dynamic but also means the conversation stays generative rather than converging. The one non-adopted reframe (toggle CTA) is a specific design detail that got lost in the broader discussion.
---
## Strengths
1. **Signal-driven recommendation in Buddy Bar section.** Morgan arrived with a specific hypothesis, ran it against data, and delivered a clear direction. V3 is a well-reasoned synthesis, not a compromise.
2. **Sean's candor about platform debt.** Openly naming the A-B test accumulation problem and mobile development gap gave the team clear permission to push for structural change. This kind of ownership is rare in client reviews.
3. **Reframe adoption across both directions.** Ideas moved fluidly from presenter to stakeholder and back — the group genuinely built on each other's thinking.
4. **Jeff's competitive lens.** His quick pattern recognition around Google Slides and the Canva competitive comparison added useful grounding without derailing the session.
---
## Improvement Areas
1. **Define V3 success criteria before building it.** The direction is clear but the test it's feeding into has no stated bar for success. Without that, the next research review will have the same problem.
2. **Separate the Polymorphic "review" from the Polymorphic "decision."** Showing four flows and asking "how does this sit with you?" generates reaction but not direction. The next polymorphic session needs a recommendation going in, not just options.
3. **End with a stated decision log.** Even two or three sentences — "We decided X, Y is Sean's, Z is happening by Wednesday" — would dramatically improve follow-through from a call this generative.
4. **Size the mobile opportunity in the room, not after.** Sean's "close to 70% mobile traffic, ~50% conversion rate" stat is compelling but appears late. Bringing that number into the Buddy Bar section would have sharpened the business stakes for everything that followed.
---
## Primary Improvement
**Introduce a hard close.** Before ending, Eric (or Bryan) should name the two or three things that were decided and ask Sean to confirm. For this call: "We're moving forward with a V3 design that combines V2 interactions and V1 labeled CTAs — who's building that, and when does it need to be in Helio for next week's test?" That one question would have converted the session from a strong review into a strong review with a committed output.
---
## Automation Opportunities
**1.**
- **Friction Observed:** Research findings presented manually from Helio — Morgan walked through signals verbally without a live dashboard, requiring significant narration time
- **Automation Idea:** Helio signal summary auto-generated as pre-read before the call — "here's what the data showed for each variation" distributed 24 hours ahead
- **Glare Block:** Measure — Findings
- **Impact:** Reduces presentation overhead, lets the call focus on implication and decision rather than data transfer
**2.**
- **Friction Observed:** Next steps were left unstated at call close; follow-up responsibility defaults to memory
- **Automation Idea:** Post-call decision + action item summary triggered by recording transcript — surfaced into Slack or Jira within 30 minutes of call end
- **Glare Block:** Focus — Decisions
- **Impact:** Catches the V3 ownership gap and polymorphic open threads before they drift into the next week without owners
**3.**
- **Friction Observed:** Sean's bet status is "scattered across various Jira tickets" with no clear owner or readiness tracking per bet
- **Automation Idea:** Bet status table generated from Jira and surfaced before weekly design reviews — showing owner, design readiness, and last test date per bet
- **Glare Block:** Lead — Organizing Work
- **Impact:** Would have changed Eric's question ("do we have a sense of status on each bet?") from an open question to a 30-second confirmation