The consultants have been with your company for three weeks. Today they present their recommendation to the engineering team. Move all the services to a single shared database to simplify operations. The senior people are nodding. You are sitting near the back, thinking about the nightly batch job that locks half your tables for forty minutes, which nobody mentioned in the interviews and which would now block everything.
It is easy to stay quiet. They are experienced, expensive, and they have slides. You are one engineer. But think about what they are working from. Three weeks of interviews, documents and diagrams. They are often very good at the general problem. What they cannot know is everything that never got written down, and some of that is in your head.
So speak, but in the form of a question. Questions are easier for everyone to hear, and they invite an answer instead of a defence. How would this handle the overnight batch job? It locks the order tables for around forty minutes every night. A good consultant will take it seriously, and may already have an answer you had not thought of. If so, you have learned something. If not, you have put a real fact on the table where it belongs.
Bring evidence if you can. A graph of the lock times, the incident from last spring, a line from the logs. Specific facts are much harder to wave away than a feeling that it will not work.
If the meeting is not the right place, or the question gets lost, write to the person who hired the consultants. Keep it short and practical. I want to make sure the recommendation accounts for this. Here is what I have seen, and here is the data. Copy the consultants if that feels right. Most of them are glad of it, because a recommendation that fails on contact with reality is bad for their reputation too.
Be prepared to be wrong. There may be a plan for the batch job further down the slides. That is fine. Asking a clear question that turns out to have an answer still shows you were thinking.
Confidence here is not about being sure you are right. It is about believing that what you know about your own systems is worth saying out loud.
– Asael Shinder
Top comments (0)