Specializing is important. But specializing while being ignorant of the context kills.
Seen a specialist edit a user manual to death? She got bogged down with relatively less important things like grammar. She didn't check the manual's usefulness in the context of the user interface.
Seen a specialist usability-test a user interface (UI) to death? He was sweating the relatively smaller stuff (like which way the Accountant's face was turned when she was selecting the Estimate option). He didn't check the UI's value in the context of the business process.
Or seen a specialist drawing beautiful pictures of processes using powerful new software tools? She didn't check the processes in the context of the enterprise.
Checking your work with an expert within your discipline might get you a pat on the back. But that's no guarantee your work will have a positive overall impact.
Specialization that ignores the context creates wasteful silos. So ... step out. Look around. Take feedback from someone in a higher discipline.
Seen a specialist edit a user manual to death? She got bogged down with relatively less important things like grammar. She didn't check the manual's usefulness in the context of the user interface.
Seen a specialist usability-test a user interface (UI) to death? He was sweating the relatively smaller stuff (like which way the Accountant's face was turned when she was selecting the Estimate option). He didn't check the UI's value in the context of the business process.
Or seen a specialist drawing beautiful pictures of processes using powerful new software tools? She didn't check the processes in the context of the enterprise.
Checking your work with an expert within your discipline might get you a pat on the back. But that's no guarantee your work will have a positive overall impact.
Specialization that ignores the context creates wasteful silos. So ... step out. Look around. Take feedback from someone in a higher discipline.