What evidence helps explain performance at work?
Work often requires analysis and coordination in the same task. You need to examine data, assumptions and constraints, and also clarify responsibility, hear objections, state limits and agree what happens next. A failed delivery does not directly establish low IQ or low EQ.
FermatMind’s current IQ entry uses 30 original matrix/visual reasoning questions. Its Beta reference is based on random simulation, not representative population IQ norms. EQ-60 is a 60-item self-report covering Self-Awareness, Emotion Regulation, Empathy and Relationship Management. Neither result establishes overall work ability or determines hiring, promotion, role assignment, pay or career fit.
This guide helps you investigate one task and choose an adjustment. It does not turn scores into occupational recommendations.
When is this useful?
Use it when an analysis keeps being revised, a handoff fails, a disagreement stalls work or a new role introduces unfamiliar demands. Moving from specialist work into management or client contact may change the tasks, but a job title does not establish a person’s analytical or relational ability.
Start with a delivery you can inspect. What needed rework? What was misunderstood? Who had to decide? These questions produce more useful evidence than an abstract judgment about your strengths.
Examine two demands in the task
Analytical demands include the information to combine, options to compare, uncertain assumptions and consequences of error. Coordination demands include the people who need a shared understanding, conflicts in priorities, unclear responsibilities, authority and available feedback channels.
A familiar calculation may require extensive coordination if the data definitions differ. A technically complex problem may have clear ownership and established procedures. Describe the task instead of labeling whole occupations as high or low in cognition, or claiming that EQ determines whether expertise can be used.
Make an initial judgment, then inspect a small piece of work. A few weeks may be a convenient window, but the review point should fit the task; it is not a validated optimal cycle.
A complete synthetic project: a reminder system that created rework
The following example is original and fictional. It is not a test item, a real user’s report or validation evidence.
The proposal, data and constraints
A small service team wants to pilot appointment reminders. Its goal is to reduce missed appointments over two weeks without adding substantial daily manual work. Four weeks of records are available, but cancellations, rescheduling and missed appointments have inconsistent labels. The budget permits changes to the existing workflow, not a new system. A manager must approve which customers may be contacted.
Morgan proposes a reminder the day before each appointment. The initial analysis shows a high missed-appointment rate, but it includes appointments canceled in advance. Before comparing reminders, confirmation requests and the current process, Morgan needs a clear event definition and denominator.
Useful analytical evidence includes the classification rule, excluded records, the reason for choosing a day-before reminder and what happens after a last-minute change. A polished chart cannot resolve an inconsistent definition. The proposal also needs contact costs, mistaken-message risks and a list of unknowns.
An objection provides information
A receptionist says, “This will add work for us.” Morgan interprets it as resistance and replies, “Just follow the process.” The observable event is a workload objection. Unwillingness to cooperate is an interpretation. The receptionist may know about calls, duplicated bookings and changes that Morgan has not counted.
Morgan returns with a more specific question: “Which step takes the most time, and which cases need manual handling?” The receptionist identifies unconfirmed changes and duplicate records. The manager explains that Morgan lacks authority to enable contact for every customer.
Morgan acknowledges the omitted costs, agrees who will record exceptions, asks the manager to approve the scope and takes responsibility for revising the proposal. This can improve information and coordination, but it does not guarantee agreement. A person with authority still needs to decide between conflicting priorities.
Why the first pilot failed
The team trials a small approved group, but sends two incorrect reminders. Staff spend time correcting them. This does not prove poor intelligence or poor emotional competence. The review finds no defined cancellation-update step, a list that becomes outdated during the day and no clear owner for the final status check.
There are also individual actions to examine. Morgan did not verify the data definition and treated an objection as a motive judgment too early. Process, resources and authority are alternative explanations; personal decisions are also relevant. Record them separately rather than choosing one global label.
A natural counterexample comes from an earlier information-review task. With clear definitions, a shared list and an assigned owner, Morgan checked exceptions and delivered on time. This weakens the claim that Morgan cannot analyze or collaborate at all. It does not erase the present error. A narrower question is whether ambiguous records and ownership make it easier to skip checks and interpret objections as resistance.
What to inspect after an adjustment
The team adds a status check before sending, uses one shared list, narrows the pilot and allows time for exception handling. Morgan circulates assumptions before the meeting and asks each responsible person to challenge them. Decisions outside Morgan’s authority remain explicitly assigned to the manager.
The next pilot examines missed appointments, incorrect messages, manual time and cases that could not be contacted. Fewer missed appointments with a large increase in staff effort may still violate the constraint. Extensive missing data warrants withholding a conclusion. Improvement after a workflow change does not establish that someone’s IQ or EQ increased.
Work samples include both proposals, classification rules, recorded objections, responsibility decisions, exceptions and outcomes. Ask specific feedback questions: “Which assumption is clearer now?” “Which step still needs explanation?” “When an exception occurs, is it clear who acts?” Those answers guide the next task more precisely than saying that Morgan became more emotionally intelligent.
Handle criticism by clarifying the issue
If a reviewer says, “This proposal does not work,” ask which requirement is unmet before defending your ability. Record what was said, your interpretation and your reaction. Then decide whether to ask for information, revise a detail or explain a reasoned disagreement.
Understanding a concern does not require accepting every request. You can say, “That change exceeds the available time. We can remove another requirement or ask the owner to revise the deadline.” Empathy does not require unlimited work or taking responsibility for everyone’s feelings.
If a pause does not help, the obstacle may be missing information, conflicting goals or an absent decision-maker. Clarify those conditions. Repeated humiliation, threats or unsafe circumstances call for support and boundaries; communication practice cannot solve every organizational problem.
Use work samples and feedback
Compare reasonably similar tasks. Did you define the problem and success conditions? Check critical information? Propose and test alternatives? Confirm responsibility and authority? Revise an assumption after an error?
Silence can reflect limited information, unfamiliar language, restricted authority or fatigue. An error can reflect a tool, a deadline or an unclear process. If no comparable task or observation opportunity exists, record that gap rather than treating the absence of a successful example as proof of inability.
Natural counterexamples help examine an original explanation. Deliberate changes help test a practical method. Keep them separate: success after adding a checklist does not retroactively prove there was never a difficulty.
Keep the useful feedback loop from a development plan
A capability backlog can be useful when it names actual gaps rather than score categories. Separate missing knowledge, missing practice, coordination problems and missing resources. Attach evidence to each item.
- Choose a current task and define a deliverable and constraints.
- Identify one analytical uncertainty and one coordination uncertainty.
- Try a small adjustment, such as checking a definition, using a limited sample, sharing assumptions or confirming a decision-maker.
- Save the work sample and specific feedback, including workload, time and authority.
- Review at a sensible milestone and decide whether to continue, change the approach, obtain support or withhold judgment.
A four-week sprint or quarterly review can be a planning choice, but it is not required and does not guarantee development. Review sooner if the task is short or new evidence changes the decision. A 12-month role target is also optional; it should not replace the immediate problem that needs evidence.
If knowledge is missing, learn the relevant method. If resources are inadequate, reduce scope or renegotiate timing. If responsibilities are unclear, agree ownership. If the work itself is unappealing, explore interests and actual activities. Do not translate every difficulty into a need for higher EQ.
Reconsider the task when your role changes, problems become less familiar, similar errors recur or feedback differs substantially from your self-perception. This is a reason to update the explanation, not to keep retaking tests until a preferred score appears.
Frequently asked questions
Is IQ or EQ more important at work?
Examine the requirements of the particular task. Analysis and coordination may both matter, but there is no universal percentage for all work. FermatMind’s scores do not establish work-performance predictions.
Does a high reasoning-test score prove suitability for complex work?
No. The 30-question original task and simulation-based Beta do not cover an entire job. Relevant knowledge, work samples, practical experience and conditions still need examination.
Does lower EQ-60 mean management or client work is unsuitable?
No. EQ-60 is self-report and is not for hiring or role assignment. Examine actual interactions, training, feedback, resources and authority instead of eliminating career options from a score.
Can an occupation be labeled low in cognition and high in relationships?
Do not use that label for a whole occupation. Tasks vary within a role, and coordination can involve difficult reasoning. Describe specific requirements and support needs.
Does project improvement prove an IQ or EQ increase?
No. Knowledge, a checklist, a tool, a workflow, additional time or clearer authority may explain improvement. Evaluate the adjustment’s contribution rather than converting it into an ability claim.
What if a colleague will not respond?
Check the channel, timing, ownership and safety conditions. Ask a short concrete question and identify who can decide. When authority is absent or conditions are unsafe, seek support rather than carrying the repair alone.
How can I begin without another long career plan?
Choose one deliverable, identify one analytical and one coordination uncertainty, make one small adjustment and keep the work sample. Review the outcome before expanding the plan.
Choose the next step by your question
For structured reflection on emotional and relational self-perceptions, visit the EQ-60 self-report. To observe one attempt at matrix/visual reasoning, visit the IQ test entry. Neither provides a career-fit verdict.
Testing does not replace work samples, relevant training, feedback or organizational resources. Career exploration also needs interests, actual activities, skills and opportunities. Review the method boundaries before interpreting results.