Just reply, "this is covered in the documentation." If they say, "I can't find where," find the broad section it's in and send them that. Then, the subsection.

Just reply, "this is covered in the documentation." If they say, "I can't find where," find the broad section it's in and send them that. Then, the subsection. Then the page. Gradually get more and more specific instead of agreeing to a meeting, but try and drag that back-and-forth out as long as possible. Don't explain the docs at any point, only send them the location of the thing you want them to read. If they say they don't understand, don't explain or agree to meet. Just get more specific. Reply slowly. If they still push for a meeting after that, schedule it so far into the future that it becomes more painful for them to wait than to put effort into understanding the docs. Make this a pattern. If that doesn't work, get Machiavellian. Schedule the meetings, but occasionally cancel those meetings (and only those meetings) on short-notice. Don't let meetings give them confidence that they will get an easy explanation by X date - make them price in a lack of reliability. Use the same strategy businesses use - make processes you want people to avoid using, unpleasant to deal with. Maybe make it clear that you see those meetings as uniquely low-priority, so the flakiness is bounded. They're doing it because it's easy to offload the responsibility onto you. It's easier to have you spoon-feed them than to pull their pants up. So you have to make it difficult, so it becomes easier for them to pull their pants up. Obviously, only use this strategy with co-workers, never with people above you. And if the docs don't answer the question, be extremely reliable and make it explicit in your response: "this isn't covered in the docs, so answering this is high-priority. The foo works by barring the snee..."