Articles · Typology

Ti vs Te: internal consistency versus external result

Ti 与 Te:内部一致与外部结果

Ti asks whether the answer is true. Te asks whether it is load-bearing — and the order of those questions is the whole argument.

Ti vs Te is not a disagreement about standards: both want to be right, and they disagree about what right means. Ti wants the model to hold — terms defined, no internal contradiction, edge cases accounted for. Te wants the thing to work in the world — delivered, measurable, owned by a name. In a meeting this is the difference between "give me twenty minutes to think about it properly" and "pick one now, we can revisit".

Neither of these is a discipline and neither is the same thing as rigour. The real disagreement is about when a decision is allowed to exist, and who pays for the delay or the rework. Below: two definitions of done, three arenas where the split becomes visible, and an agreement that gives each preference a stage it owns outright instead of splitting the difference.

Two definitions of done

For Ti, done means the answer has stopped moving: the definitions are stable, the cases are covered, and nothing in the model contradicts anything else. The test is internal, and it is applied to the answer itself rather than to its consequences. For Te, done means the answer has changed something outside itself: it shipped, the number moved, the person who owns it can be named. The test is external, and it is applied to the world.

Both tests are legitimate and neither is sufficient. A model can be airtight and useless. A delivery can be fast and measuring the wrong thing. Trouble starts when two people apply different tests to the same artefact: each experiences the other as unserious, one as sloppy and one as obstructive, and neither can say which test is right for this particular Thursday.

Ti: the answer has to hold still

Ti judges the relation between propositions. An unresolved contradiction is not an aesthetic annoyance; it produces a specific discomfort that does not fade because a deadline is approaching. So the work continues past the point where the room has moved on: chasing the definition of one word, testing an exception nobody mentioned, refusing to answer a question that has two different answers depending on what you mean.

The strength is that it catches the flaw everybody else shipped past — the metric that double counts, the policy that contradicts itself in paragraph four. The costs are two. The model's clarity can outlive its usefulness, so you keep polishing something the company has already decided not to build. And the visible cost is social: precision reads as obstruction to anyone waiting on an answer, and the more right you are, the more it reads that way.

Te: the answer has to move something

Te judges effect. The question is not whether the definition is perfect but whether the thing works and can be seen to work: who owns it, by when, measured how. Te will take a worse answer that can be executed over a better answer that cannot, and will say so without embarrassment, because an unexecuted good answer is worth zero in the only currency it recognises.

The strength is unblocking: sequencing, assigning, cutting the question down to something three people can finish this week. The costs are also two. Rework, because the decision was made before the constraint was known. And the quieter one: a Te decision tends to become defended as though it had been derived, so the organisation keeps building on a choice that was actually a coin flip, and the person who made it has to keep believing it was right.

The meeting, the review, the argument

In a meeting, Ti is the person asking what we mean by churn in minute three while Te is the person who wants a decision by minute twenty. Both are right about different risks, and both are insufferable when the other one's risk is the live one. The room usually settles it by seniority rather than by argument, which is why the same meeting happens again next quarter.

In a review, the split is about evidence. Ti wants the reasoning: why this option, what was ruled out, what would falsify it. Te wants the number and the owner: how much, by when, who is accountable. A document built to satisfy one is usually too long or too thin for the other, and the review turns into an argument about what a review is for.

In an argument between two people who live together, the same thing happens at smaller scale with more damage. "You are being pedantic" is what Te hears. "You are being sloppy" is what Ti hears. Neither sentence describes a person; both describe a stage being skipped, said at the moment when being skipped costs the most.

A working agreement: who owns which stage

The fix is not compromise, which usually produces a decision that is both under-specified and late. It is sequencing: each preference gets a stage it owns outright, and the handoff is explicit enough that nobody has to guess whether they are being consulted or overruled.

  1. Frame. Ti owns the definition stage: what problem is being solved, what would count as solved, which words are load-bearing. Timeboxed, with a written output — an unbounded definition stage is exactly how Ti loses the argument to the calendar.
  2. Decide. Te owns the decision: choose, name the owner, set the date. Ti's role here is to log objections in one place, not to reopen the frame. Logged is not ignored; logged means it has a timestamp.
  3. Build. Whoever executes owns the method. The other reviews against the framing from stage one — not against a preferred framing, and not against a definition invented at the review.
  4. Reopen. Reopening needs a named trigger: a metric, a date, a failed test. Not a feeling that the model is still imperfect, because that feeling is permanent and would reopen everything forever.

This works because each side gets the thing it cannot function without. Ti gets one guaranteed pass at the definitions with a deadline attached; Te gets a decision that will not be re-litigated on vibes. It fails in one predictable way: when the timebox is fake. A definition stage that is really a veto in disguise will be treated as one, correctly, and the whole sequence collapses back into the fight it was meant to prevent.

Where the cost lands

Ti pays in delivery. The analysis arrives after the window, and the person who did it experiences the organisation's impatience as proof that nobody cares about being correct. Te pays in rework: the thing that shipped gets rebuilt, and the rebuild is rarely attributed to the decision that caused it — it shows up later, as debt, in someone else's budget.

The agreement carries its own bill, and it is emotional rather than procedural. Te has to actually wait through stage one, which is close to unbearable when the window is closing. Ti has to accept a decision it considers under-specified, which is close to unbearable when the flaw is visible in the room. Both lose something real. If either one quietly exempts themselves, the other notices within two cycles and stops honouring the sequence.

What the letters do not decide

Expertise decides more. A Ti preference in a domain with ten years of data converges in minutes and is usually right; a Te preference on an unfamiliar problem makes fast, well-owned, expensive mistakes. Seniority, stakes, and how reversible the decision is should all move the balance more than a preference does, and none of them appear on a type description.

The vocabulary is also a hypothesis, not a measurement. Ti and Te describe two habits of judgement, and someone who speaks precisely about systems gets read as Ti even when they are Te with a good vocabulary and a taste for clean documents. The honest use of the distinction is to locate a disagreement about sequence, then negotiate the sequence — which is a thing two people can actually do.

FAQ

Is Te just Ti with a deadline?

No. A deadline makes Ti faster; it does not make it external. Te can be indifferent to internal consistency as long as the thing works and somebody owns it, and will happily leave a contradiction standing if resolving it does not change the outcome. They also fail differently: Ti fails late, Te fails visibly.

Which one is better at strategy?

Neither, and the question hides the useful split. Ti produces long-range models that can be coherent and unusable; Te produces sequences of decisions that can be early and expensive. Strategy usually needs a Ti-shaped frame and a Te-shaped cadence, which is why the pairing is common and why it argues.

How do I work with a Ti colleague who will not decide?

Give them a definition task with a deadline and a written output, then take the decision yourself once the document exists. What they need is not more time in general; it is a bounded stage where precision is the point and nobody is waiting for a verdict.

What if I am both?

Most people are, in sequence — precise about a domain they own, impatient about one they do not. Look at where you spend the extra hour, not at what you say you value. The Ni and Ne split runs the same exercise on the perception side.

Written from published type theory, community reports and observable patterns — not from a clinical sample. Framework language, not diagnosis. Updated November 2026.

Keep reading