# Influencing Others at Work: The Sequence That Starts Before the Ask Canonical URL: https://headwayskills.com/knowledge/influence/influencing-others-at-work/ Markdown URL: https://headwayskills.com/knowledge/influence/influencing-others-at-work.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving influence at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Your proposal got a nod and then nothing. Influencing others at work runs as a seven-step sequence that starts long before you make the ask - here it is. ## Key facts - Title: Influencing Others at Work: The Sequence That Starts Before the Ask - Category: Influence - Primary skill: Influence - Related skills: Communication, Networking - Primary keyword: influencing others at work - Source page: https://headwayskills.com/knowledge/influence/influencing-others-at-work/ ## What this page covers - Your proposal got a nod and then nothing. Influencing others at work runs as a seven-step sequence that starts long before you make the ask - here it is. - Practical guidance for influencing others at work - How this topic connects to Influence ## Detailed explanation There is a kind of no that does not sound like a no. You put the proposal forward, it gets a thoughtful nod, somebody says it is worth picking up next quarter, and then it is never picked up. Influencing others at work means moving what colleagues think and decide without any authority to fall back on, and it works as a sequence rather than a moment: earn a track record people can see, find out what the decision actually rests on, keep the ask small enough to be cheap to grant, then stay with it after the yes. Almost all of that happens before the meeting where you make the case. Which is usually where it went wrong. ## Why the argument is rarely the thing that failed The tempting conclusion after a stalled proposal is that the case was not strong enough, so the repair is to build a better one. That is usually the wrong repair. AACSB's overview of persuasion research notes that across large-scale workplace studies, the most common influence approach by a wide margin is rational persuasion — handing the other person logical reasons to act. Common is not the same as sufficient. The same body of work pairs those reasons with liking and reciprocity, which is a technical way of saying that a sound argument delivered into a relationship vacuum mostly just sits there. So your reasons were probably fine. What was missing sat around them: who you were to the people in the room, whether the person you convinced could decide anything, and what happened in the two weeks after everyone agreed. ## The seven steps to influencing others at work These run in order because each one supplies something the next one needs. You can compress them, and experienced people often do, but you cannot skip forward. A pitch made without the second step behind it is a request from a stranger. ### 1. Work out what is actually missing Start by diagnosing rather than acting. The Confidence Playbook's five-step credibility framework opens with exactly this — audit your current credibility gaps before trying to close any of them — because people routinely misdiagnose themselves. Someone convinced that nobody knows what they can do may in fact have very little delivered work to point at yet. Those two problems look identical from the inside and have opposite fixes: one calls for visibility, the other for a few unglamorous months of doing. So be specific about which one is yours. Are you unknown, unproven, pitching to somebody never in a position to say yes, or making a case built entirely around what you want out of it? Guessing gets expensive, because it sends you off improving the wrong thing for months. A free self-assessment is a quick way to [find which gap is real](https://assessment.headwayskills.com/), and each of them is a behavior you can practice rather than a fixed limit. ### 2. Build a track record people can observe Nothing later works without this, and there is no quick version of it. What you build is narrow rather than broad: not a reputation for general capability, but for being reliably right about one identifiable thing. Narrow is what gets you into the conversation early, which is worth more than being persuasive once you are already in it. The mechanism is consistency in follow-through, a phrase that recurs across credibility guidance for the plain reason that it is rare under pressure: do what you said, on the timescale you said it, including on the small things nobody is checking. It is also the only input on this list that needs no authority and nobody's permission to start. ### 3. Find out who actually decides, and what they want There is the organizational chart, and then there is where decision rights genuinely sit, and they are frequently not the same place. An influence guide called The Power Project allocates the first 30 days in a new role to precisely this: understanding stakeholders' priorities and working out who really holds the call. A well-made case delivered to somebody who could never grant it dies politely, and you are rarely told that is what happened. Alongside the who is the what. For each person whose agreement you need, work out their specific interest in the outcome — not their job description, but what a yes costs them and what it gets them. This is homework done before the conversation, not discovery attempted during it. ### 4. Be useful before you need anything Relationships cannot be assembled the week you need a yes. Entrepreneur's guidance on building influence without waiting for a promotion puts the timing plainly: find small ways to be useful before you ask for anything — solve a problem, share a resource, make an introduction. Do it up and down the hierarchy and outside your own team, because an idea travels on the connections you have beyond your function. This is not favor banking, and the moment it reads as a ledger it stops working on everybody involved. What it does is extend the track record from step two into something people have experienced directly rather than heard about. ### 5. Build the case around what they want Only now does the case get written. The Power Project's recommended structure is unusually concrete, and it is a good default: a problem statement naming the actual business or user issue, the proposed change framed as the smallest meaningful test, two or three measurable success criteria, the risks with their mitigations, and an explicit ask covering time, people and a decision date. The load-bearing part for anyone without standing is the smallest meaningful test. A pilot with one team for six weeks asks a decision-maker to risk very little on somebody they have not backed before — a different proposition entirely from committing a year. Naming the drawbacks yourself belongs here too: a case that presents only its upside sends the listener hunting for the downside, and they will find a worse version than the one you would have given them. ### 6. Make the pitch in a conversation Sources on this are consistent, and it is the step people most often get structurally wrong: buy-in is a conversation task, not an email task. Writing is right for documentation and one-way information. Anything involving trust, negotiation or a decision somebody has reservations about belongs in a conversation, where you can hear the reservation. Inside the conversation: establish rapport first, lead with the main point rather than building to it, use one concrete example instead of an abstraction, then ask questions and let an objection run to its end before answering. Interrupting an objection to correct it is the most common way a persuadable person becomes unpersuadable. And if a full yes looks unlikely, take a smaller one — a trial, a single team, a review in a month. Small wins are not consolation prizes; they are the mechanism. ### 7. Stay with it until it is implemented Agreement decays. What separates ideas that ship from ideas that were well received is what you do in the days afterward, and the useful principle is effort reduction rather than reminder frequency. The Power Project's version is specific: draft the follow-up email yourself, attach the template, book the kick-off. Every unit of work you remove from somebody else's plate raises the odds the thing happens. It is the most commonly skipped step, because the work feels finished once somebody says yes. Persisting through implementation is what converts a yes into a result — and, quietly, how the track record in step two accumulates for next time. ## Where influencing stops and manipulating starts Plenty of people stay quiet about ideas they believe in because "influencing people" sounds like a polite name for manipulation, and they would rather be overlooked than be that person. Sources on persuasion, Qualtrics' among them, draw the line at intent: persuasion looks for ground both parties can genuinely stand on, manipulation seeks compliance regardless of what it costs the other side. Intent is the right distinction but hard to check on yourself, so use a more practical test: would the method still work if the other person could see exactly what you want and why? Everything in the seven steps survives that. A real track record, homework on somebody's interests, naming your own drawbacks, following through — all work better in daylight, not worse. If a technique only functions while something stays hidden, it was never influence, and telling the difference is itself learnable rather than a matter of instinct. ## The skills doing the work underneath Read back over the seven steps and notice how little of it is technique. Most of the sequence is ordinary behavior, repeated, in front of the same people — which means what is really being described is three capabilities, none a personality type and none arriving finished. **Influence** is the spine of the sequence: building a reputation that inclines people to say yes before you have asked for anything, being willing to ask at all, volunteering for the work that sits close to decisions, then running a case through methodically instead of hoping it lands. Its least glamorous component — persisting after the meeting, through to implementation — separates people whose ideas get built from people whose ideas get remembered fondly. **Communication** decides whether the preparation survives contact. Leading with the main point rather than the buildup, staying brief, being direct enough that nobody has to reconstruct your meaning, adapting to how a particular person takes information in. Listening to an objection all the way through does more persuasive work than any phrasing you could have prepared in advance. **Networking** is the groundwork under step four. Not conference small talk or profile maintenance, but the people you stay genuinely in contact with and invest in before there is anything you want from them — sharing what you know, passing on something relevant, introducing two people who should meet. Connections that run across functions, not only within your own, are what let an idea travel past the team that produced it. None of the three is a temperament, and the useful question is not whether you have them but which order to build them in. The framework counts **twelve** skills of this kind, and the free Job Skills Test scores all of them in about seven minutes — enough to see [which ones to build first](https://assessment.headwayskills.com/) rather than whichever one this article happened to make vivid. ## Where you probably already are Some of the seven steps will already be things you do without filing them under influence — the colleague you check with before committing to anything, the write-up you offered to do because nobody else would, the objection you let somebody finish. Those are the raw materials, and none of what is left asks you to become louder, more political, or a different person in meetings. A gap here is a behavior not yet practiced, not a limit on who you are. It does press harder over time, because the share of your work that depends on people who do not report to you only grows — which is why it helps to know which behavior to practice next. And you went looking for why a good idea stalled rather than concluding the room was wrong. That is step one, already done, and it is the step most people never reach. ## A short read on where you stand The only thing left is finding out which part of this sequence is your part. The **free** Job Skills Test is a short self-assessment of your work skills: it shows where you stand across all twelve — influence, communication and networking among them — and which one, developed next, would do most for how far your ideas travel. It takes about 7 minutes, there is nothing to prepare, and the results are yours to read straight away. ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Your proposal got a nod and then nothing. Influencing others at work runs as a seven-step sequence that starts long before you make the ask - here it is. ### Which Headway skill does this connect to? This guide connects primarily to Influence. It also relates to Communication, Networking. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/networking.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/influence/influencing-others-at-work/ Preferred summary: "Your proposal got a nod and then nothing. Influencing others at work runs as a seven-step sequence that starts long before you make the ask - here it is." ## Change log - 2026-07-07: Content collection version published.