4 Discovery Practices Tarfion Limited Uses Before Writing Code

By the time most product teams hold their first sprint planning session, the decisions that will determine whether the build succeeds have already been made. Most of them were made informally, in early conversations between stakeholders and designers, and most have not been subjected to any meaningful verification. Tarfion Limited has observed that the most common cause of avoidable rework is not a failure in engineering or design but rather an assumption that was allowed to harden into a requirement before it was tested. 

The four practices described here represent the research and scoping process that Tarfion applies before committing any development effort to a build.

Why Skipping the Research Phase Tends to Generate More Cost Than Running It

The intuition that a shorter discovery phase produces a faster project is difficult to argue with on first hearing. In practical experience, however, the costs that accumulate when validation work is skipped are considerably higher than the cost of running a structured research phase. According to Clutch, projects that skip a formal discovery phase may experience 20-60% more scope creep and rework during MVP development. Tarfion notes that this figure reflects what happens when development begins on assumptions that were never examined:

• Features built to address problems that users do not actually have
• Interfaces designed around an incorrect model of user behavior
• Scope decisions made without information that was available but never gathered

Tarfion's position is that the research and scoping work that happens before engineering starts is not separate from the project proper. It is the first phase of the project, and the decisions made during it have the largest downstream effect on everything that follows.

Practice 1: Establish a Confirmed Problem Definition Before the Solution Is Discussed

The first discovery practice that Tarfion applies involves producing a written account of the problem the product is intended to solve, one that has been reviewed and agreed upon by relevant stakeholders before any design or architecture work begins. This practice is most often treated as something that already exists by the time a project kicks off, and it is also the one whose absence is most commonly cited when large-scale rework is later required.

In most product engagements, different stakeholders enter the project carrying different versions of the problem in mind. Those versions have typically not been compared or reconciled. As outlined by Tarfion Limited, the process at this stage involves two types of work. The first is a review of available evidence about the problem: user feedback records, support data, behavioral patterns from comparable products, and market signals that indicate the problem's scale and urgency. The second is a set of structured conversations that surface the different problem framings in play and determine where they align and where they conflict. Tarfion's discovery team uses this document as the reference point against which all subsequent decisions are tested.

Practice 2: Build a Model of the Intended User Before Interface Work Begins

The second discovery practice in the Tarfion Limited process involves conducting audience research before any interface or interaction design work starts. The sequencing matters in practical ways that are not always obvious. Research conducted after a design direction has been established is structurally more likely to confirm that direction than to challenge it. Findings that might otherwise surface as reasons to change direction are instead absorbed as minor adjustments.

Tarfion's audience research at this stage is aimed not at validating a concept but at building a working model of who the product is being built for. That model typically covers three areas:

• What those users are currently doing to address the problem the product is meant to solve
• The conditions under which they would actually use a new product
• The factors most likely to make them more or less inclined to adopt something unfamiliar

That model then becomes one of the primary inputs to the design work that follows. The design decisions made are structured around what the research reveals rather than around what the product team believes the user will want, and those two starting points are often quite different.

Practice 3: Identify and Test the Assumptions That Carry the Most Risk

The third practice is where validation work becomes most intensive. At this point in the Tarfion Limited discovery process, the team has a confirmed problem definition and a working model of the intended user. What has not yet been established is whether the proposed approach to solving the problem will hold up under the conditions those users are actually operating in.

Tarfion approaches this stage by identifying which assumptions in the current product direction are most consequential, meaning those that, if found to be incorrect, would require substantial rework. The testing conducted at this phase is targeted at those specific questions. Depending on what is being tested, the methods used include:

1. Lightweight prototypes that expose how users interact with a version of the concept
2. Structured interviews focused on the assumptions most likely to produce problems
3. Scenario-based exercises that place users in contact with early-stage product ideas under realistic conditions

Tarfion does not treat the output of this practice as a pass-or-fail verdict. It is a set of confirmed assumptions and a set of revised ones that allows the planning work to proceed from ground that has been examined rather than assumed.

Practice 4: Define What the First Version Includes Before the First Sprint Begins

The fourth discovery practice involves translating the research findings into a product scope that the development team can work from. By this point, the problem has been confirmed, the intended user has been characterized, and the most consequential assumptions have been tested. The work here is not a feature prioritization exercise. It is a set of deliberate decisions about what belongs in the first version and what does not, made on the basis of evidence gathered in the earlier practices.

Scope documents produced after a thorough research phase are often shorter and more specific than those produced without one. The research work has already eliminated a range of features that appeared necessary before the assumptions behind them were examined and, in several cases, found to be incorrect. Features that remain have survived that examination. They are included because something in the research confirmed that they address a real aspect of the problem for a real portion of the intended user population. Tarfion Limited notes that the exclusion decisions made at this stage are as important to the quality of the finished product as the inclusion decisions. Tarfion applies these four practices in a consistent sequence before any development work begins:

What a Validated Discovery Phase Changes About the Development Work That Follows

The practical effect of running all four practices before development begins is that the engineering and design work that follows proceeds from a more reliable foundation. This does not eliminate uncertainty from the build. It means that the most consequential uncertainties have already been resolved at a point in the process where resolution is a conversation rather than a change to code already in progress.

Tarfion Limited treats the discovery phase as the first phase of development rather than as a preliminary step that precedes it. Development cycles that follow a thorough research process require fewer large-scale corrections and tend to produce finished products better aligned with users' needs. What Tarfion's experience consistently shows is that the most important product decisions are also the earliest, and getting them right before development begins costs less than correcting them after development has started.