There's a quiet kind of power in a keyboard shortcut, and that power deserves more attention. The user's question is simple: how does someone who doesn't use a mouse extend a formula down a column? The answer they're looking for is straightforward, but the fact that they have to ask at all says something important about how we design for productivity. We still assume the mouse is the default tool, even when we know better. That's not a criticism of the user. It's a signal that our tools and our documentation often lag behind the people who use them.
For anyone building a process document or a spreadsheet for others, this is a reminder to think about the full range of ways people work. The drag-and-drop method works fine for some, but it's not universal. Keyboard-only users are not an edge case. They're often the most efficient people in the room, and they're the ones who will notice when a process breaks down. The practical fix here is to include the keyboard equivalent in your instructions, right alongside the mouse click. That means naming the specific keys, not just saying "use the shortcut." It's a small addition that can save someone a lot of frustration, and it makes your documentation more useful without making it longer or more complicated.
What stands out is the care the user is putting into their process document. They're not just writing for themselves. They're writing for others who may not share their comfort level with spreadsheets. That's the right instinct, and it's worth carrying that mindset further. When you document a workflow, you're making a choice about who gets to participate in it. If you only describe the mouse method, you're quietly excluding people who don't work that way. If you include the keyboard path, you're telling them their way of working matters. That's not just polite. It's practical. It means fewer questions, fewer errors, and a process that actually works for more people.
The next time you're writing instructions for a spreadsheet or any other tool, ask yourself what you're leaving out. Then add the alternative method, even if it feels obvious. The user is already on the right track by asking the question. The rest of us should follow their lead.