INTERACTIVE EXPERIENCE · NO DATA COLLECTED

This should be quick, right?

The request seems simple.

Let's see where this request needs to fit.

Before changing anything, we need to understand what surrounds it.

Existing architecture

Code structure

Technologies in use

Dependencies

Processed data

Storage

Existing files

Data flows

Business logic

Existing APIs

Automated tasks

Active processes

Authentication

Permissions

Input validation

Sensitive access

Hosting

Server configuration

Backups

Production environment

Running services

Availability constraints

A change never exists in isolation. Its impact depends on the system it needs to integrate with.

Does the request still seem that simple?

LET'S FOLLOW THE DIAGNOSTIC

YOUR REQUEST A seemingly simple need

ENVIRONMENT Understanding the existing system

ARCHITECTURE Structure and dependencies

DATA Flows and storage

PRODUCTION Services already running

SECURITY Access and permissions

BUSINESS LOGIC Rules and processing

INTERACTIONS APIs and processes

IMPACT What the change may affect

DIAGNOSTIC COMPLETE INTERVENTION

Scope identified Dependencies understood Risks assessed Constraints identified Impact estimated Approach defined Intervention prepared

1 POINTS ANALYZED

You asked for a change.

Before developing it, we needed to understand where and how to intervene.

No analysis. No risks assessed. No impact identified. Nothing to diagnose.