Scope note: the three passages below are editorial composites that describe only how the two communicate and organise information, not handling procedures. Anything involving a property contract, title registration, a mortgage or tax follows local law and professional guidance from a lawyer or bank; anything involving product safety or industry compliance follows the regulator and professional advice. Where a situation is unclear, seek help first and then act on that guidance.
Working together on a launch, one more often watches "when we must ship" and the other "whether we are actually ready when we ship". Both are needed, and friction usually appears when the date and the basis do not line up.
Setting the rhythm for a product launch
(Fictional scene.) Six weeks to launch, only twenty units have arrived, creator bookings must be locked four weeks ahead, and the channel has promised a date verbally without signing. One approach works backwards from resources: how the twenty units split across core channels, how much of the gap a booking-based trial can cover, and what has to be renegotiated if the channel date moves. The other confirms whether the missing build would change what users can actually do with the product. Either approach can be used by the same person, and the order depends on the task and the information available.
Both lines have to land on the same sheet, and two cases can be handled separately. If only the communication material is not ready — copy, assets, demo script — keep the public purchase date and set a clear content review date, changing no public commitment before it. If the core feature does not meet the agreed release criteria, move the date; or, after stating the scope and the limits honestly, open a limited trial and write the unavailable features into the public description.
The costs sit on either side. Shipping on time holds the window, but the first reviews set the shape; moving the date protects the experience, but channel and creator schedules must be renegotiated, and the cost lands on relationships and time. Which is better depends on where the acceptance line is drawn, what the contract says about penalties, and how much capacity the team really has — not on type.
A checklist helps: split the launch items into two columns, "must hold before we ship" and "better if it holds", and give every item a checkable condition and an owner. Anything without a condition is recorded as insufficient information and the facts are gathered; anything in the second column that nobody objected to needs checking whether it has no owner or is genuinely unimportant, rather than being assumed unimportant.
The follow-up: whether to delay for a principle
(Fictional scene.) This continues the previous discussion, same launch and same people, with the meeting moving from scheduling to "should we move the date". The side arguing to ship usually lays out the cost of delay as checkable items: channel slots, the competitor window, two weeks of team capacity; and asks the other side to say what a delay buys back. The side arguing to delay usually states first what has to be protected: which gap would be remembered in the version shipped on time, and how long it would take to repair afterwards.
The disagreement is usually not about who cares more about the product, but about which basis each cites. A workable move is to put both sentences into checkable form: ask the delay side to write "which signals appearing would show that shipping on time really did damage the experience"; ask the ship side to write "which single condition failing would move the date immediately". With both written, the meeting has a shared basis.
Being unable to produce a metric does not mean there is no basis, and does not mean avoidance. It may be insufficient information (no data on user response yet), different standards (one looks at first reviews, the other at long-term reputation), or simply something not easy to say in the room. Work out which, then decide what information to gather and where to hold the conversation.
Two friends buying a small flat together
(Fictional scene.) Two friends who have known each other for ten years want to buy a small two-bedroom flat together, each paying half the deposit. One approach starts from executable terms: ownership shares, who lives there, how the mortgage is split, and what happens if one wants to sell in a few years. The other tests whether the relationship can bear those terms: how to raise it if one of them marries and needs the flat, and whether talking about money will damage a ten-year friendship. Either approach can be used by the same person, and the order depends on the task and the information available.
Both preparations have a cost. The one who sets terms first may make the other feel "you already planned the exit"; the one who talks about the relationship first may postpone what should be written down until prices and rates have moved. The difference is closer to where Te and Fe put their effort — one turns shared property into executable terms, the other first checks whether the relationship can hold those terms — but either order can work. Keep the counterexamples: at this amount, INFJ may also demand the terms be written first; when the other person is clearly uneasy, ENTJ may also leave the numbers alone for now.
The friends can bring their questions about ownership, financing and exit terms to qualified local advisers. The example focuses on the conversation. An exercise: each writes one line, "how I would want to exit in the worst case", without debating right and wrong, read them aloud, then each explains the concern behind the line. If someone changes the wording while reading, ask whether they changed the term or the concern, rather than deciding they have not thought it through.