The following fictional examples show how people might handle the same information. Either type can do any of the tasks. Assign work according to experience, access, authority and availability.
Before the stream, agree on who can answer a question, which facts can be shared and who will follow up if an answer is unavailable.
### ESFJ and ISTP: an upset viewer reports a faulty product
In a fictional livestream, a viewer says a product stopped working after three months and that they were sent between support teams. Both colleagues can log the case and check the warranty status. Neither can authorise compensation.
One part of the response is to understand what the fault has disrupted and what the viewer hopes will happen next. Another is to check the purchase date, model and support record. Either colleague can gather both kinds of information.
Confirm what the team can do and who will follow up. If the outcome is still uncertain, say which details need checking. Either person can respond with care while sticking to what is known.
### ESFJ and ISTP: a cousin asks about three cameras
In a fictional example, a cousin who wants to start making videos shares the same budget, list of three cameras and specification sheet with two relatives. Both have the same information about how the camera will be used.
One consideration is how each option would fit the cousin’s needs, including weight, ease of use and access to repairs. Another is whether each camera meets the same recording requirements, such as stabilisation or the length of a continuous clip. Either person can weigh both.
A camera that meets the recording requirements may be awkward to carry. A light camera may fall short of the quality or recording time the cousin needs. Those are trade-offs to evaluate using the same criteria.
If a comparison is possible, have the cousin film the same short scene with two candidates. The test can reveal handling and usability differences. It does not reveal either relative’s type.
### ESFJ and ISTP: when a livestream loses its connection
In a fictional livestream, the connection drops forty minutes in. Both colleagues can see the same status information and use the same approved alert and backup options. Neither yet knows when the stream will return.
One useful contribution is an audience update stating what is known and when the team will update them again. Another is checking the approved backup and recording what is still uncertain. Either colleague can take either task if they have authority.
If the team knows the next update time, it can share that without promising when service will resume. The choice to post or check the backup depends on the information and assignments, so it cannot identify a type.