Digital strategy
SQDA method: decide what to improve on a website
Your website attracts criticism and the proposals keep coming: redesign the interface, publish more content, improve visibility, automate. But which problem does each proposal address, and why start with that one? Before committing a budget, you need to understand the connection between what has been observed and the choice being proposed. This article offers a way to make that reasoning explicit without requiring a full dossier for every adjustment. With SQDA, you can qualify a signal, select a useful check, justify an intervention or keeping what exists, then define what would make you reconsider the choice.
Short answer
Make the reasoning behind a choice visible
Its central proposal is that a website decision should make both its rationale and the conditions for reconsidering it visible. It helps business owners understand why one intervention comes before another, and helps teams identify what still needs checking.
Intervening, keeping what exists, deferring or investigating further are all possible outcomes. SQDA supplies neither an automated diagnosis nor a priority score.
Start with the situation
A perception can open an investigation
“Our website looks dated” is a reported perception. “A prospect asked whether this button sent their details” is a question received, provided a record exists. “The button returns an error in this scenario” is a direct observation. A count of recorded submissions over a stated period is a measurement. These signals have different origins and different limits.
To qualify them, record who reports what, on which page, in what context and on what date. A documented qualitative difficulty can justify a targeted correction. There is no need to invent a metric to lend weight to a precise observation.
A signal is separate from its suspected cause. Few enquiries may reflect an unsuitable offer, an irrelevant audience, a misunderstanding or a functional failure. “We need to redesign the interface” is already a proposal. Before adopting it, state which choice needs clarification and which checks could help.
For choices about audience, offer or website role, the strategic review worksheet applies SQDA. Its two-file comparison shows why the same unsuitable enquiries can call for either an execution correction or a strategic decision.
Four steps
The four steps of SQDA
Start with the objective, the journey concerned and its boundaries: for example, enabling someone to prepare an enquiry from a service page, in French, on mobile. This scope gives the four steps something concrete to address.
| Step | Working question | Record to keep |
|---|---|---|
| S — Signal | What has drawn our attention? | Origin, date, page, context, type of signal and limitations. |
| Q — Question | What must we clarify before choosing? | Decision question; plausible explanations where needed; a check that could distinguish them. |
| D — Decision | Which choice should we make, and why? | An action verb, options actually considered, rationale and relevant constraints. |
| A — Action | Who does what, when, and how will it be checked? | Task or documented retention, owner, deadline or trigger, verification and condition for review. |
Verification belongs to the Action step; what it reveals can become a new signal and open another examination. A question is not a hypothesis: “Is the first click understood?” opens an investigation; “the label suggests immediate submission” offers an explanation to test. Similarly, “UX” names an area of work; “check understanding of the first click before changing its label” states a decision.
From Q to D
Choose evidence proportionate to the decision
A check should be capable of changing a decision. Before gathering information to choose a course of action, write down what each result would change: correct, retain, investigate or defer. If no plausible result would alter the next step, the collection may not be needed for that choice. Exploratory research remains legitimate; describe it as an effort to discover the questions.
The level of evidence depends on risk, cost, reversibility and uncertainty. A reproduced failure often justifies a bounded repair followed by a repeat test. Replacing an entire journey calls for more examination, including its dependencies and what already works. Statistical evidence is not required to correct an established labelling error.
Compare the dimensions that matter in the case: expected benefit, effort, risk, dependencies, timing or team capacity. State what remains unknown. SQDA prescribes no universal score or weighting.
Keeping a page because its content already meets the need is a choice. Deferring a redesign until the offer has been clarified can be another: name the condition for resuming it.
Plan three separate checks
- Implementation: is the intended change correctly in place?
- Observable result: does the intended behaviour occur in the scenario checked?
- Business effect: have enquiries or sales changed, and is there evidence to attribute that change?
A repaired form confirmation establishes a functional result; it does not demonstrate more enquiries. Record the check, then reconsider if the expected effect is absent, an unwanted effect appears or the context changes. Keep the earlier decision and its rationale: revision should not erase how the team reached its position.
Observed on 6 October 2026
Does the first click prepare or send the request?
On the Edikka Contact page, “Prepare my request” is followed by “Nothing is sent at this stage. You will review everything before submitting.” This promise deserves a simple check: does the behaviour match the words? It is the technical starting point for the comprehension question illustrated in the UX reassurance example.
Observed signal (direct observation)
A specific promise to check
The public page distinguishes preparation from submission. The signal here is the displayed text, recorded on 6 October 2026. The check has one objective: establish whether the first button accurately describes the next step, in French and English, on mobile and desktop.
Decision question
Should the label stay?
If the click only prefills the next part of the form, “Prepare” fits. If it transmits information, the button should announce submission and the supporting text should change. Observing the fields, focus and network requests distinguishes these two possibilities.
Reasoned choice
Keep “Prepare my request”
The 6 October check shows that the click copies the goal, blocker and email address into the next form, then moves focus to the first-name field. The status confirms: “Request prepared. Add your contact details, review everything, then submit.” No network request was observed in the three seconds following activation in any of the four scenarios checked.
Two labels were considered here: keep “Prepare my request” or announce submission. The first describes the observed behaviour; the second would imply transmission that does not occur at this step. The decision is therefore to retain the current wording.
Check and review
Repeat the check when the journey changes
The check used Chrome, keyboard activation and fictitious inputs, in French and English, at widths of 390 and 1,440 pixels. Final submission was not activated. The technical owner should repeat this check whenever preparation or submission changes; the content owner should then review both language versions.
Behaviour matches the wording within this scope. Visitor understanding and the effect on enquiries remain to be assessed. If hesitation is subsequently documented, the next check should examine what people expect to happen before they click.
Documented decisions
Three retrospective readings of the audit register
The public register, edition 1.2.5 reviewed on 6 October 2026, lets us read three decisions through SQDA. This correspondence is proposed retrospectively.
Rule out unnecessary work
Observed on 5 September and reviewed on 5 October 2026: the GEO offer existed on the SEO page. The absence finding is withdrawn and no additional page is created. Reading the offer changes the decision.
Repair a journey
On 6 October 2026, an empty confirmation despite HTTP 200 leads to a fix to shared initialisation in FR/EN. The register subsequently records visible confirmation and receipt of acceptance-test enquiries.
Keep a conclusion undetermined
Reobserved on 5 October 2026: the field reports consulted supply no data. The search for this edition is closed; field performance remains unknown.
None of these decisions measures a business effect.
Contribution and limitations
SQDA, OODA, PDCA and PDSA: connections and limitations
Reuse the framework
A record for your next decision
Copy the four headings into your usual working document. Start with this short version; expand the record when risk, cost or disagreement calls for more detail.
The minimum version, in four lines
Signal. The Contact button promises preparation without submission — observed on 6 October 2026.
Question. Does the first click fulfil that promise?
Decision. Keep the label: four FR/EN checks confirm prefilling, with no network request observed after the click.
Action. Technical owner: recheck whenever the journey changes; revisit the wording if the behaviour changes.
The full record for a decision with greater consequences
Signal. Objective and journey concerned: … Scope: … Signal, origin, date and context: … Type and limitations: …
Question. Choice to clarify: … Plausible explanations: … Useful check: … Result that would change the next step: …
Decision. Intervene, retain, defer or investigate further: … Options actually examined: … Rationale, constraints and remaining uncertainties: …
Action. Concrete next step: … Owner: … Deadline or trigger: … Implementation check: … Expected observable result: … Business effect measurable or unknown: … Condition for review: … Date and reason for any revision: …
Before sharing the record, check that another person can understand the choice, find its source and identify an observation that could change it. Use “unknown”, “not relevant” or “to check” when that describes the available information.
Use it, then discuss it
Start with a choice you are unsure about
At Edikka, SQDA structures a decision. The Compass provides an initial orientation; the Decision Centre’s territories group related subjects. The collaboration process organises an assignment. A project brief then specifies deliverables and acceptance criteria when the choice commits the team to a redesign.
Take one pending decision about your website. Write down the signal, the question to clarify and what would change your mind. You can then choose a proportionate next step, including keeping what exists.
A question for discussion: what information is enough to commit to a change, and when does documenting a choice cost more than it contributes? Bring Edikka an example or counterexample, with its context and the choice it challenges.
Further reading
Sources
- John R. Boyd, The Essence of Winning and Losing, January 1996 document, September 2012 edition; OODA sketch on PDF page 4.
- Deming Institute, PDSA Cycle: learning and the PDSA/PDCA distinction. Accessed 6 October 2026.
- ASQ, Plan-Do-Check-Act Cycle: stages and repetition. Accessed 6 October 2026.
- Michael Nygard, Documenting Architecture Decisions, 15 November 2011: recording rationale and retaining decisions.
- Edikka audit register, ADA05, ADA21 and ADA07: edition 1.2.5, reviewed 6 October 2026; each record retains its own dates.
To check the evidence behind a recommendation before applying this guide, consult the SEO claims register.
Prompt, full source and citation
Explore this analysis.
Choose a task, review the prompt and take it to your AI.
SQDA method: decide what to improve on a websiteUpdated October 12, 2026
Read the full prompt
Your inputs stay in this browser until you paste them into your AI. No analysis runs here.
Your AI cannot read the link?
Copy the full source or download the document, then attach it to your conversation.
Edikka · View the passage
What would you like to clarify in this passage?
The passage and its source accompany your question. You then choose your assistant.
Paste the question into your conversation. Nothing is sent automatically.
Full message to copy
No message is sent from this page.
Review and publish the post yourself on LinkedIn.
Every intervention should have a reason.
With SQDA, we put reasoning at the heart of the relationship: start with what has been observed, explain the choice and agree on what would change the next step.
Make the choice understandable.
The client and the team should be able to connect a recommendation to the signal that prompted it. Explaining the options and the rationale gives everyone the means to discuss the choice.
Match the intervention to the need.
Correcting, retaining or deferring can each be the right choice. We adapt the investigation and the intervention to the stakes, the risk and what is already known about the journey.
Plan for review.
An owner, a check and a trigger for review give the choice a practical next step. What we learn afterwards helps us confirm the decision or reconsider its rationale.
A useful recommendation makes clear why to act, why now and under which conditions to change course.
Frequently asked questions
Additional answers to clarify the key points covered in this article.
What does SQDA mean?
SQDA stands for Signal, Question, Decision, Action. Edikka formalises this framework to connect a qualified observation, a question to clarify, a justified choice and a next step with its verification.
How does SQDA differ from a digital audit?
An audit examines a defined scope using its own methods and evidence. SQDA helps explain a decision based on those findings or other signals. It does not replace the audit protocol.
Can you decide with insufficient data?
Yes, if the choice and its verification are proportionate to risk, cost and reversibility. A documented qualitative difficulty can justify targeted action. State what is unknown and what would trigger reconsideration.
Does SQDA replace OODA, PDCA or PDSA?
No. These frameworks already include decision, testing, checking or learning. The Deming Institute distinguishes PDSA from PDCA. SQDA proposes Edikka’s formulation for discussing website choices.
Can SQDA be used without an Edikka assignment?
Yes. You can reuse the record shown in the article in your own working document, acknowledging Edikka’s formalisation. Adjust the detail to the decision; no software or Edikka engagement is required.