--- title: "The keyboard shortcut that made people think I was better at my job than I actually was" date: 2026-08-07T00:00:00Z updated: 2026-09-11T11:47:29Z tags: ["Career", "Excel", "Judgment", "Visibility", "Efficiency"] canonical: https://bianca.codes/blog/the-keyboard-shortcut-that-made-people-think-i-was-better-at-my-job/ --- # The keyboard shortcut that made people think I was better at my job than I actually was _One keyboard shortcut convinced people I was better at my job than I was. That's a real career lever, and a trap: fluency with a tool gets mistaken for judgment about what it actually shows._ Someone shares their screen on a call and asks, "how much data do we actually have here." They start scrolling. Ten seconds pass, then twenty, thumb dragging down a scrollbar past row after row of a spreadsheet nobody has bothered to turn into a table. You reach over, hit Ctrl+End, and the cursor lands on the exact last row instantly. Small pause. Someone says "how did you do that." You explain the shortcut in one sentence. The moment passes. Nobody in that room remembers the explanation. They remember that you knew, instantly, and they didn't. That one moment did more for how people saw my judgment than most of the actual analysis I did that quarter. Over the following months I got pulled into conversations I hadn't been in before, handed the "can you just look at this and tell me if it's right" requests that used to go to someone more senior. The pattern was obvious in hindsight: the person who can move through a spreadsheet like they already know its shape gets assumed to also know what's true about the numbers inside it. The uncomfortable part isn't that the reputation was wrong. Ctrl+End really does require understanding how Excel tracks a used range, and that's a real, useful piece of knowledge. The uncomfortable part is that it's a much smaller piece of knowledge than the reputation implied, and treating the two as the same thing is a decision with consequences for what gets handed to you next. ## Fluency with the tool isn't judgment about the data, and nobody in the room can tell the difference live In a meeting, nobody can watch your reasoning. They can only watch your output and how long it took to arrive, and that's a genuinely cheap signal to read. Instant navigation proves exactly one thing: you understand how Excel's data model behaves, that a contiguous block of cells has edges the software can jump to. It proves fluency with the tool. It does not prove you understand this data, where it came from, or whether the row Ctrl+End just landed on is actually the last real row. That last part is where the trap gets specific rather than abstract. Ctrl+End jumps to the last cell Excel has ever touched, not the last cell with real data in it. A stray format applied to row 40,000 three years ago, long since cleared of content, will still make Ctrl+End land there, past thousands of genuinely empty rows. Someone fluent enough to navigate instantly can be just as fluent at confidently reporting the wrong answer, because the shortcut never asked them to question what it found. Speed can demonstrate a mistake exactly as convincingly as it demonstrates a skill, and from the outside the two look identical. That's the actual trap in the hook. Once you're the person who moves fast, people stop routing you the tasks the fast navigation ever tested, and start routing you the judgment calls it never touched, whether this number is trustworthy, whether this dashboard is safe to show leadership. The appearance of competence gets you handed the harder job before you've necessarily built the skill underneath it, and the gap doesn't announce itself until something is wrong and your name is on it. ## Three things that actually close the gap **Narrate what the fast thing proved, out loud, in the moment it happens.** After the Ctrl+End, say the second sentence: "that gets us to the edge of the used range, doesn't tell us if everything in between is actually populated." One sentence turns a trick into a demonstrated piece of judgment, and it costs you nothing except being slightly less impressive for three seconds. **Build the boring depth before you're tested on it, not during.** People will assume you have the underlying judgment the moment they see the tool fluency. Spend real, unglamorous time on the parts that don't look fast, validating totals against a second source, checking for the gaps a quick scroll would hide, understanding where a dataset actually comes from, so the first time you're asked to vouch for a number isn't the first time you've actually checked one. **Decline the leap when it's premature, with a specific reason, not a vague one.** "Happy to look at this, give me until tomorrow to actually check it rather than eyeball it in the meeting" names the real gap between glancing and verifying without undercutting the fact that you're capable of doing the check properly. It reads as rigour, not hesitation. ## This week Next time something you do reads as impressively fast to someone else, whether it's a shortcut, a formula, or just knowing where a number lives, add the one sentence about what it actually proved and what it didn't. You're not committing to narrating everything forever, just running the experiment once and noticing whether the room's read of you shifts from "fast" to "fast and careful," which is the reputation actually worth having. This is the first of three posts this month on the gap between looking competent and being competent in Microsoft 365 tools, more on the other two shapes it takes later in August. ## Frequently Asked Questions ### **Isn't pointing this out just a roundabout way of showing off how fast I am?** That's a fair thing to be wary of. "Watch how quick I am" is showing off. "Here's what that quick thing did and didn't confirm" is information the other person needs before they act on what they just saw. The test is whether you'd say the second sentence even if nobody was impressed by the first one. ### **What if my manager starts assuming I can do more than I've actually proven, based on stuff like this?** That's the exact trap the post is about, and it's worth naming to them directly rather than hoping it self-corrects. When you're handed something that assumes depth you haven't built yet, say so plainly: "I can take this on, I haven't validated something like it before, so build in time for me to check my own work the first time." That converts a silent assumption into a stated, manageable gap. ### **Does this apply outside Excel, or is it specific to spreadsheet shortcuts?** The mechanism is the same anywhere speed is the only visible signal, a fast Power BI demo, a quick Word mail merge, a Teams automation that looks effortless because the setup happened off-screen. Anywhere someone can only watch your output and not your reasoning, the same gap between looking fluent and being right can open up. ### **How do I actually build the judgment part, not just the appearance of it?** There's no shortcut for this one, deliberately. It's checking your own numbers against a second source before you present them, asking where a dataset actually comes from instead of assuming it's clean, and sitting with the boring validation work often enough that it stops being the thing you skip under time pressure. The speed was earned through repetition; the judgment gets earned the same way, just on less visible tasks. ### **Is it different if I'm early in my career versus already senior?** The mechanism is identical, the stakes scale with what gets handed to you off the back of it. Early on, the gap between looking fast and being right mostly costs you a correction and some awkwardness. Senior, the same gap can put a wrong number in front of leadership with your name attached, which is exactly why naming it out loud gets more valuable, not less, the more people assume you've already closed it. ### **What if I genuinely am as good as the fast moments make me look?** Then the sentence costs you nothing and confirms what people already believe, which is a fine outcome too. The point was never to undersell real skill, it's that "I looked fast, therefore I'm right" is a leap other people make on your behalf whether or not the leap is warranted, and you're the only one positioned to check it before it becomes someone else's assumption to build on.