Skip to content

Knowledge centre

Clearer decisions. Technology put to better use.

Guides, criteria and practical resources to connect your business with technology.

Answer your next question.

5 publications

Ninety-day roadmap divided into three months with priority review.

Evolve

How to build a 90-day technology roadmap

A 90-day roadmap is not a wish list with dates: it is a decision about what to do first with the capacity you actually have. This guide explains how to define goals, prioritize, map dependencies, estimate capacity, and review the plan each month.

Criteria to evaluate technical debt by impact, likelihood and dependencies.

Evolve

How to identify technical debt that is already affecting the business

Technical debt is not just a developers' problem: it becomes a business problem when every change takes longer, errors recur, or no one dares to update. This guide explains how to recognize symptoms, gather evidence, estimate risk and prioritize, without diagnosing blindly.

Before-and-after comparison to measure the value of an automation.

Evolve

How to measure whether an automation delivers value

An automation can work technically and still not deliver value if nobody uses it or if it generates more exceptions than it solves. This guide explains how to measure with a baseline, usage, time, errors and exceptions, and how to track results without inflating them.

Definition of a software improvement from the problem to its acceptance test.

Evolve

How to request a software improvement without leaving scope open

A request expressed in one sentence often returns as something different from what you expected. This guide explains how to write a requirement with the problem, user, scenarios, rules, acceptance criteria, constraints and change handling so everyone understands the same thing before starting.

Comparison between project-based development and monthly technical capacity.

Evolve

Project-based development or monthly capacity: how to decide

Hiring development as a fixed project or on a monthly capacity basis is not a matter of price, but of how well you know today what you need. This guide compares both modalities according to scope, uncertainty, continuity and ways to prioritize, without addressing rates or contracts.

Tools to put it into practice.

Browse all resources
Ninety-day roadmap divided into three months with priority review.

Evolve

90-Day Technology Roadmap

CSV template to build and review a 90-day technology roadmap: objectives, initiatives, prioritization criteria, dependencies, estimated hours, status and monthly review.

Before-and-after comparison to measure the value of an automation.

Evolve

Record of results and adoption of automations

CSV registry to track an automation's results: baseline, usage, time, errors, exceptions with root cause and decision per period. Helps distinguish between an automation that works and one that delivers value.

Definition of a software improvement from the problem to its acceptance test.

Evolve

Requirement Sheet and Acceptance Criteria

Markdown sheet to request a software improvement with problem, users, scenarios, rules, acceptance criteria in Given-When-Then format, constraints, out-of-scope items and change log.

Criteria to evaluate technical debt by impact, likelihood and dependencies.

Evolve

Technical debt register and actions

CSV register to document technical debt with symptom, evidence, business consequence, risk, priority and action, so technical conversation becomes an investment decision.

From knowledge to practice.

Explore how we connect business and technology in real projects.

Explore real projects