Designing a website or application — training

It covers the design, construction, and deployment methodology. It does not teach a language: the principles remain valid whether you write the code, hire someone, or assemble no-code tools.

The eight modules

1. Decide what to build — The problem statement that sorts good ideas from bad, with a weak example and a usable example. Why your real competitor is a spreadsheet. The replacement rule: why 20% improvement never replaces anything. The three-pass cutting method, and the "not now" list.

2. Investigate without deceiving yourself — The four rules of a useful interview. A complete 35-minute interview guide, ready to use. A reading grid for responses: what is a signal, what is nothing.

3. Design before building — Write user flows in text, including the line everyone forgets. Reduce the path to the first useful result. The seven states of each screen — empty, loading, nominal, error, partial, too much data, offline. Write useful error messages, with a before/after table.

4. The data model — The six questions before fixing a schema: uniqueness, historization, deletion, permissions, units and time zones, growth. Why a referenced price instead of a copied one changes the amount of your old orders. The four tables everyone forgets. Two-step migrations, without service interruption.

5. Choose your technique — The only true criterion. No-code, with code, or in between, with the limits of each. The six building blocks you never write yourself. Six questions to evaluate a third-party service you will depend on.

6. Build — Deliver in vertical slices. The right quality, at the right time. Diminishing returns testing. Ten non-negotiable security points, from access control on guessable identifiers to rate limiting. Backups, and the two numbers that determine your setup.

7. Deploy — Accessibility in ten points, with WCAG AA thresholds. The three performance indicators and their thresholds, with the five levers by yield. Minimal observability. A 24-point launch checklist in five blocks.

8. Maintain, and know when to stop — Three indicators, not thirty, plus cohort retention. Translate user requests into real needs, with a correspondence table. Manage technical debt with its triggers. Handle an incident in five steps. The written criterion that will tell you whether to continue or stop.

What you take away

• Eight concrete deliverables, one per module
• A complete user interview guide
• The seven screen states grid
• The ten-point security checklist
• The 24-point launch checklist
• A review grid before each production release
• The list of the ten most costly errors
• A glossary of 10 terms

For whom

Freelancers and small teams launching a digital product, project managers who will oversee a service provider, developers who know how to build but not what to build.

For whom it is not

Those looking to learn programming: the training assumes that construction is resolved, one way or another. Nor for teams already operating large-scale systems.

What the training does not cover

Learning a language, natural referencing (SEO), paid advertising, fundraising, recruiting a technical team, and very large-scale system architecture.

Format

PDF, approximately 5,300 words divided into 8 modules and 3 appendices, with a required deliverable at the end of each module. Immediate access after purchase.

No commercial results are promised: a technically flawless product that meets no need does not sell better than a shoddy product. The technical thresholds cited (performance, accessibility) come from public references, indicated each time — check their current version.