“You’re the product manager. Just talk to the customers.”
“Engineering only needs to code and test. Why involve them now?”
“Finance can put the numbers into Excel afterwards.”
You hear the sentence and think about everything it leaves out: the assumptions you challenge, the risks you assess, and the decisions you help others make. Perhaps you begin explaining your entire job. Perhaps you stay quiet because challenging a senior person feels risky. Later, you replay the conversation and wish you had answered differently.
The word just can make a whole profession feel small. Customer conversations, coding, testing, and accurate spreadsheets all matter. The problem begins when a leader treats one visible activity as the full scope of a role—and organizes the work around that incomplete understanding.
Responding well starts with identifying what needs to change. If the situation involves humiliation, discrimination, or retaliation, seek appropriate support. A better explanation of your role may not address the underlying problem.
Why does a leader come to see your work this way?
“Finance just fills Excel sheets” may reveal an understanding of work that has never been examined. Several explanations are possible, and they can reinforce one another.
They may be repeating what previous managers taught them
Imagine a manager whose former boss regularly described finance as administration, engineers as implementers, and product managers as people who collect customer requests. Those descriptions may become the categories through which they understand the organization. After promotion, they repeat the same language, perhaps believing it demonstrates commercial focus.
Research on organizational socialization describes how people learn about their roles and organizational environment through experienced colleagues and role models. Applying that perspective here, inherited professional stereotypes are one plausible explanation—not proof of any particular manager’s motives. Bauer and colleagues’ review provides the broader research context.
“I’d like to understand what you’ve previously expected from finance. Has the team mainly provided reporting, or also challenged assumptions before decisions?”
This creates room to examine an inherited expectation. Having learned dismissive language from someone else does not remove a manager’s responsibility for how they speak today.
They may see the output while missing the judgment
A spreadsheet is visible. The reasoning behind it may be much harder to see. A manager receives a forecast but may never hear about the inconsistent assumptions corrected, the scenarios compared, or the uncertainty that remains. Working software does not reveal every architectural decision; a short product recommendation may conceal weeks of investigation.
Professionals can contribute to this gap when they communicate only completion: “The report is ready.” Consider making the contribution clearer:
“The report is ready. We found that the expansion plan depends on an assumption we haven’t validated. I’ve included two scenarios and a recommendation for what to check before committing.”
The deliverable is now connected to a decision. It is worth examining whether you have made your reasoning accessible or assumed that the finished work would explain itself.
The professional may have room to take more initiative
Sometimes a broader contribution has neither been demonstrated nor discussed. Someone may wait for requests, deliver exactly what was asked for, and assume leadership will eventually invite them into strategic conversations. Meanwhile, the manager interprets that pattern as the intended scope of the role.
“I’ve noticed we involve finance after the commercial assumptions are agreed. Could I review those assumptions earlier on the next proposal and show where our analysis can help?”
Choose a real business problem, bring evidence, and propose something useful. Complexity alone does not establish value: explain how your contribution improves a decision. Also check whether the broader responsibility belongs to your role or is an expansion you want to negotiate. Initiative does not automatically grant decision authority.
There may be reasons someone has stayed quiet: previous suggestions were rejected, workload leaves little capacity, or speaking up has carried consequences. Explore those conditions before concluding that the professional failed to show initiative.
The organization may reward the narrow version of the role
Consider a finance team measured almost entirely on reporting speed and accuracy while leaders say they want a strategic partner. If information arrives after decisions are made and no time is allocated for analysis, the team’s behavior may reflect the job as designed.
CIPD’s guidance on job design treats roles and responsibilities as part of how work is organized. The working arrangement itself belongs in the discussion.
“If you want us to challenge the commercial assumptions, we need earlier access to the proposal and time for that review. Which existing work should take lower priority?”
Sometimes the dismissal concerns authority
Expertise can complicate a leader’s preferred decision. Finance may question an optimistic forecast. Engineering may challenge a promised deadline. Product may bring evidence against a favored feature.
Calling those people “spreadsheet fillers,” “coders,” or “customer interviewers” can weaken their standing in the discussion. Whether deliberate or habitual, the language tells the room whose judgment deserves attention.
Research by See and colleagues across four studies found that greater power was associated with less advice-taking, with elevated confidence helping explain the relationship. This supports considering overconfidence as one possible mechanism; it does not establish why a particular manager makes derogatory remarks.
Watch when the language appears. If a manager welcomes your expertise until it challenges their preferred answer, explaining your job again may not resolve the disagreement about your authority.
Explore the gap without accepting the insult
Both sides may have work to do. The professional can make their contribution clearer and initiate a discussion about expectations. The manager must remain curious, define responsibilities fairly, and treat people respectfully.
“I may not have made the reasoning behind our work visible enough, and I’d like to improve that. When our role is described as ‘just filling spreadsheets,’ it also makes it harder for the team to raise concerns. Can we clarify where you expect our judgment and challenge?”
Understand what felt dismissive
You may feel your expertise has been overlooked, worry that exclusion will make delivery harder, or be expected to own an outcome you cannot influence. Each concern points toward a different request.
“I felt frustrated because I’m expected to deliver this project, but the scope was agreed before I could assess its implications.”
Separate what happened from what you believe it means. “They don’t respect me” may eventually prove accurate. Initially, distinguish a careless phrase, a misunderstanding, and a repeated pattern of exclusion.
Clarify responsibility before defending the title
A leader may lack context, be focused on an urgent deliverable, or have deliberately defined a narrower role than you expected.
“When you describe my role that way, do you mean my part in this particular task, or my overall responsibility? Which outcomes do you expect me to own, and which decisions should I contribute to?”
Titles do not establish identical responsibilities everywhere. Product, engineering, and finance roles vary across organizations and seniority levels. If your leader explicitly wants a narrower role, discuss expectations, evaluation, and whether the position fits your professional direction.
Explain the decisions behind the deliverables
A long list of meetings and tasks can still leave a leader unsure why your involvement matters. Connect your judgment to a decision, using an example within your actual responsibilities.
Product management: “Customer conversations help us understand the problem. I assess that evidence alongside business priorities so we can recommend what deserves investment.”
Engineering: “Before implementation, we need to assess dependencies, reliability, and maintenance. Early involvement lets us explain what is feasible and where the trade-offs are.”
Finance: “The spreadsheet records the analysis. Checking assumptions and interpreting scenarios helps the business understand what its commitments could mean.”
Bring evidence: an assumption corrected, a dependency identified, or a recommendation that informed a decision. Explain your contribution accurately, including where results were shared with others. You do not need an inflated savings estimate to demonstrate useful judgment.
Respond briefly in the moment
A public meeting rarely offers space to explain an entire profession. A short clarification can protect the immediate decision:
“There’s a feasibility decision here that needs engineering input before we commit. I can explain the main dependency now.”
Or: “We can prepare the spreadsheet. Before the numbers are used, we also need to validate the assumptions behind them.” Keep the intervention tied to the issue being decided. Arrange a separate conversation if the broader misunderstanding persists.
Discuss a specific incident
“You never understand what I do” communicates frustration but offers little concrete information. The Center for Creative Leadership’s Situation–Behavior–Impact framework suggests identifying the situation, describing observable behavior, and explaining its impact. Its extension adds an inquiry into intent.
“In Tuesday’s planning meeting, the delivery date was confirmed before engineering reviewed the dependencies. We now need to assess whether the commitment is feasible. What was driving the decision to confirm it at that point?”
Listen before making your request. The leader may have faced a deadline you did not know about or believed a review had already happened.
“For the next commitment, could we include a short engineering assessment before the date is confirmed?”
Understanding the pressure can help you propose a workable process. It does not require agreement with the original decision.
Turn understanding into an agreement
Clarify the outcomes you own, the decisions you can make, where your advice is required, and when you need to be involved. Discuss the time and information those responsibilities require.
If your scope is reduced, establish who takes on the remaining work: “If my role ends at gathering customer feedback, who owns turning that evidence into a prioritization recommendation?”
If accountability remains broad, explain the support it requires: “If I’m accountable for the forecast, I need access to the assumptions behind these commitments and time to review them.”
A leader can reasonably disagree with your recommendation. Clarifying decision ownership distinguishes being consulted from having final authority. Afterwards, send a brief recap of what was agreed, including unresolved points.
Make your contribution visible through ordinary work
A concise update can include the decision, the evidence, your recommendation, and remaining uncertainty:
“We reviewed the three requested integrations. Two fit the current architecture; the third adds a maintenance dependency. We recommend starting with the first two and reviewing the third after the pilot.”
This makes judgment visible alongside output. Keep it proportionate: additional reporting should serve a decision rather than become a second job devoted to proving that you work.
Recognize when explanation has reached its limit
After clarifying the role, watch what changes. Does the leader involve you at the agreed stage, adjust expectations, or acknowledge a trade-off when choosing a different recommendation?
If they repeatedly exclude your expertise while holding you accountable for the consequences, more explanation may have limited value. Keep factual records of relevant commitments and decisions. Seek support from an appropriate manager, trusted senior colleague, or internal channel. Consider whether a different team or role would offer a workable match between responsibility and influence.
Being clear can improve a conversation. It cannot guarantee that another person becomes receptive.
Leave with a clearer position
You deserve respectful treatment even when someone disagrees with your assessment. You also need clarity about what you are responsible for and the conditions required to deliver it.
The next conversation might establish an earlier review, clarify one decision, or resolve one mismatch between responsibility and authority. Before it, separate the event, your reaction, and the change you want to request.
DeepMirror’s check-ins and AI coaching feedback can support that reflection and help you develop a practical next step. Explore inner clarity and communication at work, or start a private check-in to prepare your conversation.
Sources and further reading
- CIPD. Job design.
- Bauer et al. New Horizons for Newcomer Organizational Socialization: A Review, Meta-Analysis, and Future Research Directions.
- See, Morrison, Rothman and Soll (2011). The detrimental effects of power on confidence, advice taking, and accuracy.
- Center for Creative Leadership. Use Situation–Behavior–Impact to understand intent.
The workplace scenarios and suggested wording are illustrative examples. The hero image is AI-generated.