The following case stories describe actual engagements. Client and program names are omitted to protect confidentiality. Technical standards, domain contexts, and outcomes are reported accurately.
The Implementation can be Right, and Still be Wrong
Sometimes the key to a solution lies in discovering the questions that have not yet been asked. A large multinational corporation developing a crucial piece of a new DoD system was stymied. Even with their huge team of experts, they had been unable to resolve a technical issue. They had the skills and technical acumen, but needed a fresh perspective.
A New Trick Can Save the Day
Medical device manufacturers face a steep regulatory burden. Even the least critical medical systems must receive FDA approval before they can be placed on the market. This Fortune 500 medical device manufacturer was preparing to ship an important, but low-risk upgrade to a stalwart family of institutional medical equipment. Then at the last minute, the program hit a wall – at least it looked that way.
Find the Right People, Ask the Right Questions
Technical jargon can sometimes be overwhelming, especially when the customer is a foreign company whose employees speak English as a second language, if they speak it at all. Sometimes, a seemingly insurmountable difference can be resolved by a quick sidebar conversation between the right people.
An Architectural Solution to an Integration Problem
People can become accustomed to inconvenience and expense when it seems inevitable. A large group of engineers attempting to integrate a complex group of applications in an equally complex device containing a large collection of sensors – why should that be easy?
Keep Calm and Carry on
Generally, market forces evolve over time. Sometimes they are altered overnight by events outside anyone’s control. When that happens, organizations do not just need speed. They need people who can integrate quickly, work across boundaries, and help keep important work disciplined while the pace changes around them.