Boundary of use: the three scenes below are editorial fiction, used only to compare two possible trade-offs; they are not for dividing work and not for typing. Either type can do user research, and either can do interviewing, coding and write-up well; competence depends on training, experience and the requirements of the task.
One researcher may want to improve the guide while another wants to check how the records will be compared. Agree what the guide needs to accomplish and how you will judge the evidence. Either person can raise either issue.
ENFP and INTP: designing a user-interview guide
(Fictional scene) The same task: eight new users, forty minutes each, finding out why something was installed and then not used, with a formatted record due in three days.
One approach writes the entry as a question that invites a story: not why don't you use it, but when did you last open it and what were you doing then; plus two softening sentences so the person does not feel interrogated. The other splits "not using it" into three situations — never used, used and stopped, switched to another product — and writes a decision rule for each, so the eight records can be compared afterwards.
Each has a cost. The first may dig out unexpected reasons, but the eight records may end up with entirely different themes, making it hard to say anything about prevalence; the second is more comparable but may turn the interviewee into an answer machine, and the real reason never surfaces. The cost has nothing to do with preference; it relates to research experience, deliverable requirements and the mix of interviewees.
A workable arrangement runs in two parts: a story-style entry first, branch-style follow-ups after, with the lengths adjusted to the interviewee's state. That is not a fixed recipe and does not map to a type; experienced researchers switch back and forth within one session. Stopping to compare notes after the third interviewee is only an example, not a threshold. The review looks at four things: whether the phrasing led the answer; whether the answer gave a specific experience bearing on the research question; whether similar answers came from independent mentions; and whether different answers might just be sample variation, since new users and long-standing users face different situations.
Speaking up more is a clue, not proof that the entry worked; one nod or one "more or less" cannot stand alone as evidence for a conclusion.
ENFP and INTP: can this conclusion go into the report
(Fictional scene) Eight interviews done, three interviewees mention too many notifications, so they turned it off. One candidate sentence sits on the table: users generally find notifications excessive. Two reactions are both possible.
One leans toward writing it in: those three raised it unprompted, the words were specific, and it supports a detailed paragraph. The other leans toward narrowing: the questions were not identical and the sample is eight, so the most that can be written is that the phrasing appeared in this round; "generally" goes beyond the material.
In this fictional report review, an observation can be worth recording even when it cannot support a claim about users in general. Both researchers need to distinguish what was said from how far the conclusion can extend.
A workable approach records the number of mentions and the asking conditions. This round can be written as: three of eight interviewees raised excessive notifications unprompted; those three mentioned it under the following phrasings. The asking conditions have to be stated: whether it came from an open question, from a follow-up, or from a list of options. If neither can be written, put it under to be verified rather than in the main conclusion. No type thereby gets a lower evidential bar.
ENFP and INTP: a cousin wants to drop out and learn programming
(Fictional scene) When a younger relative asks for direction, two lines of questioning are both possible. He is in his second year, wants to leave university for a bootcamp, and says he could be employed within six months.
One line asks about experience and motive first: have you written a line of code, have you asked anyone doing this work, what is it you actually want to leave. The other breaks the path and the conditions first: front end or back end, what the bootcamp teaches, what goes on the CV in six months, whether you could return to university afterwards.
Discussing the person’s reasons can clarify what they hope to change. Checking entry requirements, costs and realistic next steps tests whether an option is feasible. Either person can ask both sets of questions. Neither approach establishes a type or makes the decision for the student.
The check can be handed to him: write two lines — how many hours a week I can give over the next six months, and what I will have to show for it at the end — then read the bootcamp's contract and refund terms and talk to someone studying or working in the field. Both lines have to be in his hand; someone answering for him does not count. This kind of decision is not divided by type, and is not made by someone else on his behalf.