--- title: How to Write a One-Page Behavioural Thesis Before You Commit to a Format description: Committing to a format too early stalls progress. Learn how a one-page behavioural thesis helps you clarify the real problem before design begins. image: https://weareaffective.com/hubfs/learning-centre-images/how-to-write-a-one-page-behavioural-thesis-before-you-commit-to-a-format.webp --- [Skip to content](https://weareaffective.com/learning-centre/how-to-write-a-one-page-behavioural-thesis-before-you-commit-to-a-format#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # How to Write a One-Page Behavioural Thesis Before You Commit to a Format Table of Contents A team spends three weeks debating whether to build a native app or a progressive web app. Another team argues for six months about whether their onboarding should be five screens or eight. A founder rewrites their landing page copy four times before anyone has spoken to a single real user. The format question pulls people in early because it feels like progress. It is visible, discussable, and produces something you can point to. The actual question, what [behaviour are we trying to change](https://weareaffective.com/user-psychology-app-design), and why do we believe that is possible, gets deferred until the format demands it, and by then the format has already constrained the answer. > Before the format question, there is always a behaviour to change and an emotional shift to earn. What we call a behavioural thesis is simply a single page of thinking that settles three things before the format decision gets made: what the person currently does, what they need to feel differently about, and what would count as evidence that the shift is realistic. Getting those three things onto one page forces a level of clarity that teams routinely skip. And skipping it is expensive, because every format choice made without it is really just a guess dressed up as a decision. The one-page behavioural thesis is a forcing function. It makes the team commit to a specific human being doing a specific thing in a specific context, and it asks whether the product genuinely has a mechanism for changing that. If the team cannot fill the page, the format decision should wait. ## Why the Format Decision Feels Urgent (and Why It Isn't) Format decisions feel urgent because they are concrete. Choosing between an app and a website, between a quiz flow and a straight sign-up, between three onboarding screens and seven, these feel like real work because they produce outputs. Wireframes. Specs. Something to show in a meeting. The urgency is partly social. Teams need to feel they are moving, and visible artefacts signal movement in a way that a page of thinking does not. There is also a subtler pull. Format decisions are, in the short term, unchallengeable. If a team decides to build a native app, nobody can prove that was wrong until months later when the data comes back. A behavioural thesis, by contrast, makes the team's assumptions visible and testable immediately. Anyone reading it can ask whether the claimed behaviour is real, whether the emotional shift is plausible, whether the evidence is solid. That exposure is uncomfortable, and avoiding it is part of why teams reach for format decisions first. We see this pattern particularly clearly with pre-launch founders. The [pull towards competitive feature mapping](https://weareaffective.com/learning-centre/why-your-social-media-app-needs-more-than-just-pretty-design), building a spreadsheet of what competitors do, is strong because a spreadsheet validates existing opinions without the risk that a real user might contradict them. As Simon has put it, the worry is that user research might reveal the idea is wrong, or that nobody wants it. A format decision made before that research is a way of outrunning the question. The format will need to be chosen. But it belongs after the thesis, not before it. ## The Behaviour You Are Actually Trying to Change The most common mistake at this stage is describing what the product does rather than what the user currently does. A team will write "the app helps users track their skincare routine" when the actual behavioural starting point is "users buy products, use them twice, and then stop." Those are different problems, and they produce different designs. Writing the behavioural thesis forces the team to name the current behaviour precisely. Not the aspired behaviour, the current one. What does the person actually do today, in the absence of the product? What is the sequence of actions? What is the context? A wellness brand designing a [supplement subscription needs to know](https://weareaffective.com/learning-centre/why-a-charity-reorder-flow-should-feel-different-from-a-beauty-reorder-flow) whether the user currently forgets to reorder, never reaches the bottom of the bottle, or buys but never takes the product consistently. Each of those is a different behaviour, and each wants a different mechanism to change it. Precision here also surfaces whether the product is solving a real friction or a theoretical one. On a project we ran for a concierge app built for a property developer, the client came to us wanting both a building management utility and a community-building social tool. Writing out the actual behaviours they were trying to change, managing maintenance requests and forming neighbourly connections, made it clear those two goals were working against each other. We ran focus groups with social housing tenants to understand what actually builds community, and the finding was that community forms through familiarity: knowing names, interests, families. That insight led us to put the mundane building tasks inside the app and design the product to actively push people toward face-to-face conversations rather than replacing them. The format followed the behaviour, not the other way around. ## UX/UI design built around *real* psychology We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## The Emotional Shift That Has to Happen First Behaviour change almost never happens because a product is functional. It happens because something shifts emotionally before the new behaviour becomes possible. A person who forgets to reorder supplements is not failing to remember, they have, on some level, stopped feeling that the product matters. A person who abandons a fitness app after three sessions is not lacking discipline, [something in the early experience](https://weareaffective.com/learning-centre/how-to-redesign-an-onboarding-flow-for-the-emotional-state-the-user-actually-arr) made the effort feel disproportionate to the reward. The behavioural thesis asks the team to name the emotional shift explicitly. What does the user need to feel, that they do not feel now, for the behaviour change to happen? This is harder than it sounds, because it requires moving past functional descriptions. "The user needs to find it easy to reorder" is a functional description. "The user needs to feel the product is working for them before the bottle runs out" is an emotional one, and it points to very different design decisions. > The interface should do the emotional work, not just describe the state it wants you to reach. This distinction matters in every detail of how a product behaves. In a meditation app teardown we conducted, the [breathing animation on the opening screen](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl) was already slowing users down before they had read a single word. The interface was doing the calming. That is the mark of design that understands the emotional shift required, it does not describe a calm state, it produces one. A product that tells users they will feel good is doing something categorically different from a product whose mechanics make them feel good immediately. Naming the emotional shift also protects against a common design trap: adding features to solve what is actually a feeling problem. If a user feels unseen by a brand, more filters will not fix it. If a user feels nervous about committing to a purchase, a longer product description will not fix it either. Name the emotional state the user is in before they open the product, and the emotional state they need to be in before they will change their behaviour. The gap between those two states is the design problem. ## What Counts as Evidence the Shift Is Achievable A behavioural thesis without evidence is a wish list. The third section of the page asks the team to state what they know, not assume, know, about whether the emotional shift is realistic for this audience in this context. This is where the thesis either holds up or falls apart. Evidence here does not have to be proprietary research. It can be analogous products that have achieved a similar shift, behavioural patterns from adjacent categories, or findings from early user conversations. What it cannot be is competitive feature analysis, because features are not evidence of emotional outcomes. Knowing that a competitor has a five-step onboarding flow tells you nothing about whether users complete it feeling equipped or feeling exhausted. The distinction between test conditions and real-world behaviour matters here. When users review a flow in a usability session, they assess it functionally and rationally, because nothing is actually at stake. In a real transaction, the emotional state is completely different, and small elements that looked fine in testing can erode trust enough to cause drop-off. Evidence gathered in conditions that match the real emotional context is worth far more than evidence gathered at a comfortable remove. We found this directly on a fitness social network, where we redesigned the location-sharing flow to introduce approximate proximity rather than precise location, and to sequence conversation before location disclosure. Conversion from sign-up to successfully meeting another user rose from roughly 20% to around 60-70%. That jump came from understanding the emotional state of a person being asked to share their exact whereabouts with a stranger, and designing around the anxiety that produces, rather than the functional task alone. If your evidence for the emotional shift being achievable comes only from what competitors have built, stop. Build the case from what users have said or done instead. ## How Framing the Ask Changes What You Learn The way a team asks users about their experience shapes the answer they receive. This is true in research, and it is equally true inside the product itself. A behavioural thesis is partly a discipline in asking the right questions, of users before the product is built, and of users inside it once it is live. On a travel app project we worked on, users were being asked to rate their holiday experience. The framing, "rate this experience", reads as something that benefits the company, and people are less inclined to engage with it unless something went wrong. We reframed the copy to ask what the user would tell other travellers about the experience. The underlying request was identical. The emotional meaning was different: now the user was helping people like themselves, not feeding data to a faceless organisation. Engagement with the prompt improved because the ask made sense in a way the original did not. The same logic applies to how teams frame questions during discovery. "Do you want a feature that lets you track your progress?" will almost always produce a yes, because it is a hypothetical that costs nothing to agree with. "Walk me through the last time you wanted to know how far you'd come" produces a real memory, with real friction points and real emotional texture. A well-constructed behavioural thesis captures what framing the team will use when gathering evidence, because the framing determines whether the evidence is real or artefactual. Small changes in how a question is posed can reveal the emotional shift that needs to happen, or conceal it entirely. Before running user interviews to build your thesis, write the questions down and ask yourself: does each question surface behaviour, or does it invite users to speculate about features they do not yet have? ## When the Format Becomes Obvious A completed behavioural thesis does not necessarily point to a single format, but it significantly narrows the field. Once the team knows the specific behaviour they are trying to change, the emotional shift required, and the evidence that the shift is realistic, format choices that cannot support that mechanism drop away on their own. Consider what the thesis reveals about the role of the product in the user's life. A product trying to change a behaviour that happens once a week in a calm, considered context is a different design problem from one trying to change a behaviour that happens in three seconds while the user is distracted. The first has space for depth and layering. The second needs to do its emotional work before the user has consciously decided anything. On a health and wellbeing product we ran, we tested two versions of a multi-step flow: one that told users upfront how long the process would take, and one that showed a progress bar without any time expectation. Without the upfront framing, drop-off rates sat at around 80-85%, typically within the first three or four questions. After we introduced that priming, setting expectations before the process began, completion rates rose to approximately 95%. The format of the flow did not change. What changed was the emotional preparation the user arrived with, and that preparation was only possible because the thesis had named "[anxiety about an unknown commitment](https://weareaffective.com/learning-centre/what-makes-people-remember-your-app-when-they-need-it)" as the emotional obstacle to address. The format question then becomes answerable. If the emotional shift requires preparation before entry, the format needs a threshold moment, something that sets expectations before the user is inside the experience. If the shift requires a sense of control, the format needs to ask permission rather than assert it. A product asking "is it okay if we send you notifications?" earns a different psychological relationship with the user than one that simply requests access. Both end up in the same place. The user who was asked feels differently about being there. 1. Name the current behaviour precisely, not the aspired one. 2. State the emotional gap between where the user is and where they need to be. 3. Set out what evidence makes the shift realistic. 4. Identify what framing the product will use to support the shift. 5. Choose the format that can carry that mechanism. ## Conclusion The one-page behavioural thesis is not a deliverable in the traditional sense. Nobody frames it and puts it on a wall. Its value is what it prevents: format decisions made before the behaviour is named, emotional shifts assumed rather than designed for, and evidence gathered in ways that confirm the plan rather than test it. The teams that skip this step are responding to real pressure to produce visible output quickly. But the cost of that shortcut accumulates. A format chosen without a thesis gets redesigned once the data arrives. An onboarding flow built around an assumed emotional state gets rebuilt when retention numbers show the assumption was wrong. Writing the thesis takes a day. The rework it prevents takes months. The formats that feel obvious in retrospect, the ones users move through without noticing, the ones that change behaviour without announcing that they are doing so, are almost always the product of a team that started with the behaviour rather than the build. The thesis is how you get there without the detour. If you are at the point where format feels urgent but the behaviour is still fuzzy, [let's work through the thesis together](https://weareaffective.com/get-started). ## Frequently Asked Questions What is a one-page behavioural thesis? A one-page behavioural thesis is a single page of thinking that clarifies three things before any format decision is made: what the person currently does, what they need to feel differently about, and what would count as evidence that a behavioural shift is realistic. It acts as a forcing function that makes a team commit to a specific person doing a specific thing in a specific context. If the team cannot fill the page, the format decision should wait. Why do teams tend to focus on format decisions before doing this kind of thinking? Format decisions feel concrete and productive because they produce visible outputs such as wireframes and specifications, which signal progress in meetings. There is also a subtler reason: format decisions are difficult to challenge in the short term, whereas a behavioural thesis makes assumptions visible and testable straight away, which can feel uncomfortable for teams. What is the most common mistake when writing a behavioural thesis? The most common mistake is describing what the product does rather than what the user currently does. Writing that an app helps users track their skincare routine, for example, is quite different from naming the actual starting behaviour, such as users buying products, using them twice, and then stopping. Those are different problems and they produce different designs. When in the design process should a behavioural thesis be written? The behavioural thesis should be completed before the format decision is made, not after it. Choosing a format without this thinking in place is essentially a guess dressed up as a decision. The format will eventually need to be chosen, but it belongs after the thesis. Why is competitive feature mapping not a substitute for this kind of thinking? Competitive feature mapping, such as building a spreadsheet of what rivals offer, validates existing opinions without the risk that a real user might contradict them. It can feel like useful research but it sidesteps the core question of whether the target behaviour is actually changeable. A behavioural thesis requires the team to confront that question directly. What happens if a team skips the behavioural thesis and goes straight to a format decision? Every format choice made without a behavioural thesis is really a guess, and guesses at this stage are expensive. Teams can spend weeks or months debating native apps versus progressive web apps, or the right number of onboarding screens, without ever establishing whether the underlying behavioural shift they are hoping to create is realistic. The format then constrains the answer rather than serving it. What counts as evidence that a behavioural shift is realistic? The thesis asks the team to identify what would genuinely count as proof that the shift they are aiming for is achievable, before any building begins. This means going beyond internal assumptions and looking for signals that the claimed behaviour is real and that the emotional shift required is plausible. Without this, the team has no honest basis for the decisions that follow. Is this approach relevant for early-stage founders as well as established teams? Yes, the article highlights that pre-launch founders are particularly prone to skipping this step because the risk of user research revealing a flawed idea feels high. Reaching for format decisions or competitive spreadsheets first is a way of avoiding that exposure. Writing a behavioural thesis early forces founders to test their assumptions before the format choice locks thinking in. ## Related Articles [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.