- The problem the project needs to solve, in one sentence
- Who will use the system day to day
- The real budget and timeline constraints
- The existing systems the new project will need to coexist with
Lethavia / Resources
Resources
Practical checklists for preparing a project, whoever ends up building it.
Practical guides
Tools that clarify the work before implementation
Each guide brings together questions and checks that reduce blind spots at the start of an initiative.
- Describe the current process, even informally
- Name known edge cases, not just the ideal case
- Specify what absolutely must work in the first version
- Separate what's necessary from what would just be nice to have
- Who visits the site and what they need to accomplish there
- Existing content to migrate, if any
- Who will update content after launch
- Necessary integrations (payment, forms, analytics)
- The features essential to the first version
- The devices and browsers to prioritize support for
- Existing accounts or external APIs already available
- A simple indicator to know if the first version is working
- Navigate the whole page with keyboard alone, no mouse
- Check that every image has a meaningful alt text
- Check text contrast against its background
- Check that forms clearly announce their errors
- Dependencies and their support status
- Presence or absence of automated tests
- Incidents or slowdowns already encountered
- The people who still understand the system today
- The task is repetitive and follows clear rules
- An error in this task has a real cost
- The tools involved have an API or integration path
- Someone can validate the result early in the automation