Design exploration · Dwellog product users

Five ways to turn behavior into personas.

These are disposable interaction prototypes, not production UI. Each preserves observed evidence while asking the user to make a different amount of the process explicit.

Personas / New Persona SetConcept A · guided builder

Step 1 · Audience

Who are we trying to understand?

Start with the audience in product language. Source names and IDs should not define the set.

Audience name

Environment

Why do you need these personas?This frames interpretation. It does not change observed behavior.

Step 2 · Primary behavior

Which activity represents this audience?

One primary source controls segmentation. Other evidence can support interpretation later.

↗

Dwellog product events

CSV · 192 events · 24 homeowners · current through Aug 1

Connected

Use as the primary behavioral source

Choose a different source

PostHog and additional CSV sources would appear here.

Step 3 · Scope

Which behavior should count?

Bound the evidence before patterns are detected. This scope becomes part of the set’s provenance.

From

Through

14 event types included

Home setup and project activity

Account creation, onboarding, properties, projects, tasks, contractors, notes, documents, and return visits.

Exclude internal and test accounts Require at least 10 homeowners per pattern

Step 4 · Assign meaning

What does success look like in Dwellog?

Assign product events to four plain-language values. Suggested events are editable and never confirmed silently.

SignupEntered the product

Required

ActivationFirst meaningful success

Required

Key valueCore behavior worth repeating

Required

RetentionEvidence of return

Optional

Step 5 · Patterns

Three patterns are worth reviewing.

These are aggregate facts, not personas. Include patterns that matter to the audience and exclude noise.

Step 6 · Persona reviewCandidate 1 of 2

Steady Home Planner

From the “Steady project managers” behavioral pattern.

Observed · locked

What happened

100% completed onboarding
Created a property and project
Returned across 3 active weeks
12 reportable homeowners

Inferred · editable

Possible motivation

Needs validation

What should we learn?

Step 7 · Publish

Your grounded Persona Set is ready.

The behavioral profiles and reviewed links are preserved underneath. The team sees usable personas first.

Dwellog product users

Production behavior · Jul 1–Aug 1 · version 1 draft

Analytics-grounded

Steady Home Planner

Organizes ongoing home projects and returns to preserve momentum.

Accepted

Careful Contractor Researcher

Builds confidence through provider detail and pricing evidence.

Accepted

Personas / Dwellog product users / Pattern studioConcept B · pattern studio

Dwellog product users

Shape personas from observed patterns

Adjust meaning, compare behavior, and curate the set without moving through separate screens.

1 · Meaning

The values used to detect patterns.

SignupActivationKey valueRetention

Evidence scope

SourceDwellog CSV

WindowJul 1–Aug 1

Subjects24

2 · Behavioral patterns

Toggle the patterns that should become persona candidates.

Steady project managers

12 homeowners · high activation · 3 active weeks

Contractor researchers

12 homeowners · pricing depth · delayed project start

One-visit explorers

11 homeowners · no activation · no return

Observed pattern

Steady project managers

These homeowners establish a property and project in one session, then return to update tasks, notes, and project status.

100%created project

3 wksmedian activity

12homeowners

Proposed interpretation

Personas / Suggested personasConcept C · review inbox

Based on 12 steady project managers

⌁

Observed behavior · locked

What this group did

Completed onboarding, created a property and project, then returned across three weeks to manage tasks and notes.

Your interpretation

What may be driving them

Ask next

What remains uncertain

Why you are seeing this

Data Disco found three reportable Dwellog behavior patterns after applying the product values your team confirmed.

AudienceDwellog users

Evidence192 events

ThroughAug 1

Review queue

Steady Home PlannerNow

Careful ResearcherNext

Early ExplorerLater

Data setup and provenance

Source: Dwellog product events
Values: account → onboarding → project → return
Privacy floor: 10 homeowners

Personas / New Persona Set Concept D · recommended setup

Start with the decision, not the configuration

What do you want to understand?

Describe the audience question. Data Disco will prepare a complete setup from available evidence and show every assumption it made.

Recommended from your data

A ready-to-review evidence plan

Built from the Dwellog product source and your audience question.

AudienceDwellog homeowners

SuccessCreates a project

Return signalViews project again

Evidence windowLast 30 days

Advanced setup

Inspect or override the assumptions behind the recommendation.

Behavior source

Primary source

Environment

Meaning map

Activation

Key value

Return signal

Evidence safeguards

Minimum group size

Exclude test accounts

Personas / Dwellog product users / Review Concept E · evidence lens

Steady Home Planner

Suggested from a reportable Dwellog behavior pattern

Editable persona story

“I want one dependable place to organize my home project, so I can return without rebuilding the plan in my head.”

Why this persona mattersThey reach ongoing project-management value.

What they appear to needContinuity, visible progress, and a trusted home record.

What to validate nextWhether return behavior reflects confidence or anxiety.

Evidence lens

The advanced trace stays attached to the story instead of becoming a separate setup workflow.

Locked

SourceDwellog product events

Scope24 homeowners · Jul 1–Aug 1

Pattern12 steady project managers

ObservedOnboarded → project → 3 active weeks

InferenceContinuity and control

Pattern controls

Keep this pattern in the set Require return activity

Minimum behavioral confidence

Developer trace

profile_version: bpv_01J...
evidence_scope:
                      esv_04A...
portfolio_prompt:
                      persona-portfolio-v3

A · Guided builder

Tests: Does explicit sequencing create trust, or feel like setup work? Most faithful to the original PDF flow.

B · Pattern studio

Tests: Can advanced users understand cause and effect better when mapping, patterns, and draft personas remain visible together?

C · Review inbox

Tests: Can the system do nearly all setup while preserving meaningful human judgment at the final interpretation boundary?

D · Recommended setup

Tests: Can a plain-language brief plus a transparent recommendation replace setup screens without hiding control?

E · Evidence lens

Tests: Can users review a simple persona story first, then reveal evidence, thresholds, and lineage in the same context?

Questions to answer before production code

Use these concepts to choose an interaction model, not individual styling details.

Q1
At what point do users understand why a behavioral pattern deserves to become a persona?

Q2
Which decisions feel meaningful, and which feel like governance paperwork?

Q3
Should “Accept persona” create the profile and reviewed relationship invisibly underneath?

Five ways to turn behavior into personas.

Who are we trying to understand?

Which activity represents this audience?

Dwellog product events

Which behavior should count?

Home setup and project activity

What does success look like in Dwellog?

Three patterns are worth reviewing.

Steady project managers

Contractor researchers

One-visit explorers

Steady Home Planner

What happened

Possible motivation

What should we learn?

Your grounded Persona Set is ready.

Dwellog product users

2 · Behavioral patterns

Steady project managers

Contractor researchers

One-visit explorers

Steady project managers

Does this feel like a useful persona?

What this group did

What may be driving them

What remains uncertain

What do you want to understand?

Steady Home Planner

A · Guided builder

B · Pattern studio

C · Review inbox

D · Recommended setup

E · Evidence lens

Questions to answer before production code