About

An independent creative technology studio.

Evidence before ornament, and one person accountable for the result.

YONTA turns unclear ideas and fragmented processes into working digital systems. Today, it is a studio led by one accountable person. That keeps the thinking, decisions and build close to the same point of responsibility.

Why the practice exists

Between an unclear idea and a working system there is usually no one accountable for the distance.

Someone has an idea they cannot quite define yet, or a process barely held together by spreadsheets, messages and manual steps.

Some implementers need a finished brief. Agencies often begin with a fixed process. The difficult part sits before both: defining the unclear idea and carrying it through to a working result.

YONTA exists to close that distance: one counterpart who thinks the problem through with you and takes ownership of building it into something that works.

What the practice does

Digital Systems is the core. The method sits inside each project, while YONTA Lab is reserved for experiments.

Digital Systems

Proof

This is the core of the practice: working systems presented through what was built and how they operate.

From Idea to Product

Method

How each system is clarified, structured and decided. The method is visible inside the work rather than offered as a separate service.

YONTA Lab

Horizon

A place for self-initiated experiments with synthetic identities. Each project is clearly labelled as experimental work.

How the work moves

A problem you can explain can become a system you can use. The work moves through three practical steps.

  1. Understand

    The unclear problem is clarified in plain language, together, before anything is built.

  2. Structure

    The decisions and the workflow are made explicit and given a structure.

  3. Build

    It is carried into a system that works and stays legible.

Accountable practice

Gencalp Islek

One accountable counterpart, from the first conversation to the working system.

Gencalp Islek leads the practice with a background in business analysis and development. Analysis, product thinking and implementation stay connected, with the same person accountable from definition through delivery.

What supports the work

These capabilities appear repeatedly across the work.

  • Requirements & problem definitionTurning an unclear need into a defined problem and a shape worth building.
  • Workflow & product architectureStructuring roles, states and decisions into one coherent system.
  • Web systemsMulti-role, responsive web platforms, built full-stack.
  • Application systemsDesktop and application software, including a Windows tool with a command-line core.
  • Implementation & validationBuilding the system, then checking that it does what it claims.

The claim is the working systems themselves.

See selected work