Examples
Breakdown
Contact

I improve how systems behave under real conditions

I identify where systems break under pressure and provide concrete corrections

Returning after a break shouldn’t feel harder than staying away

After absence, users return with reduced capacity
Systems increase pressure by highlighting gaps and lost progress
This raises the cost of returning and reinforces avoidanceAllow re-entry without exposing gaps and lower the threshold to match current capacity

When users can’t start, requiring input breaks the interaction

Users may have internal content but cannot initiate action or produce language
Interfaces that require typing or structured input become inaccessible
This leads to inactivity and abandonment
Allow entry without language or initiation using low-effort, non-verbal paths

When guidance feels like control, users resist

Systems try to guide behavior through reminders, prompts, and tracking
When experienced as control, it creates an autonomy threat and triggers resistance
This leads to disengagement, ignoring, or rejection
Preserve user ownership by keeping guidance optional, reversible, and non-enforcing

More examples

When systems create urgency, they increase pressure and reduce decision quality

Systems use countdowns, streaks, and time-limited prompts to drive action
This activates stress and narrows decision-making
Behavior becomes reactive, impulsive, or avoidantSeparate time awareness from pressure and allow action without threat signals

When intensity spikes (e.g. driving), requiring control makes behavior less stable

Users can enter fast physiological states before conscious control is available
Systems that rely on warnings or alerts add stimulation during overload
This leads to overcorrection, delayed response, or loss of controlProvide a controlled physical discharge path instead of increasing cognitive demand

How I work

I work at the level of system behavior, not surface design
These are structural corrections, not features or patterns

I review your product or flow and identify where it breaks under real conditions
I return 3–5 concrete corrections you can apply immediately

Full breakdown

One full breakdown

Re-entry

Returning after a break often feels harder than staying away.
Products surface absence and expect the same level of engagement, exactly when capacity is reduced.

Interaction failure

Products highlight absence on return:
missed tasks, lost streaks, gaps, or required explanations.At the same time, they expect users to resume at the same pace and effort level as before.This raises the threshold for re-entry and discourages return.

Mechanism

After absence, the user returns with reduced capacity.Two things happen at once:* absence is exposed (gaps, loss, discontinuity)
* task difficulty remains calibrated to the previous stateThis creates a mismatch:
lower capacity meets unchanged or high demand.* shame or self-judgment may appear
* effort feels disproportionate
* starting becomes harder than staying away

What happens in practice

The user returns with intent, but:* prior pace is inaccessible
* effort threshold is elevated
* tasks feel heavier than beforeProducts:* surface missed progress or gaps
* require catching up or explanation
* present tasks at previous intensityResult:* re-entry cost increases
* initiation is delayed or avoided
* absence extends

Correction

Allow re-entry without exposing absence and adjust demand to current capacity.On return:* no missed items or streak loss
* no gap reference
* no requirement to match prior intensityThe product:* offers a minimal next step
* reduces task size and pacing
* allows partial, low-effort engagementProgress rebuilds from the current state, not the previous one.

Contact

contact@

Text