Whether you are a Product Manager, Project Manager, or just a person handing off work to someone else, it's critical to implement the "See Something Say Something" policy. We use this in NYC, but for other reasons (see: terrorism prevention).
If there is one thing that frustrates me more than anything, it's people checking boxes and not thinking. It's one thing if the person is very junior, or has been instructed at some point to just follow the list A to Z and not to think but to just be a robot, 100% operational (poor management direction if so).
Real Life Test Case: I had some bug fixes for a screen's operations (exporting of data), and upon button click, another screen opened very noticeably within a subframe of that screen. This is obviously incorrect (think infinity mirror). While this was a mistake in my complete requirements definition, and I focused on defining the main problem with the thought that the iframe would obviously be fixed, it wasn't.
The answer from our development consultants? It was like that when we started working on it, we just fixed the functionality defined in the spec. Ok, I get it, I missed mentioning the iframe, the very noticable iframe. I'm only human. And yes, they work on our entire platform, not just that sub-function, so it could have been fixed without any other collaboration / resources.
How did I handle it?
I explained to the new development team, to See Something, Say Something. This is the point where I plead to them the following:
1. I am only human and can miss things.
2. You are all smart and we're on the same team here. If you see something that looks messed up, it probably is, TELL ME.
Whether it's developers, QA testers, the business, etc., I try to make it very clear that we're all in this together. I try to explain as much of the business reason for building what we are building to whoever wants to listen on the team in order to get them to think about whether we are doing this the right way. Some of the greatest ideas for functionality in my experience have come from the unlikeliest of sources. I fully believe that we can all learn from each other no matter what role or level, and when everyone on the team is more informed they:
1. Build Better Products
2. Look Out For Each Other
3. All Gain Knowledge
How do you handle team members who just check boxes?
How do you effectively bring together new teams?
Please tell me in the comments!