Darren Ellsworth

tl;dr Solutions change, I make sure you're not caught off guard.

Specialty: Taking problem statements and use philosophical analysis to map affected entities and solution procedures onto informatics.

For example, given the problem of "design a phone for elderly people", I wouldn't rely on personal experience to assume the wants of the elderly, nor would I assume there is one answer. I would show how the solution changes with different definitions of important words like elderly (and effected variables like location, dexterity and cognition) and provide the associated methodology for refining the problem statement given real world constraints like suppliers and shifting landscapes (technological, legal, public-sentiment, etc.).

A simple refinement of the example would be: "While factories in China are facing closures (minimal assembly), overall dexterity rates are on the decline (minimal weight and touch interaction) and [other qualifiers each with a methodology for monitoring and reacting to], how would you minimally design a phone capable of the core features of talk, messaging, video-calls, [others] for elderly who are still mobile and alert enough to locate a lost device with audio assistance, are distrusting of unfamiliar technology and [other behaviorals like associated challenges and routine samples] that can later be upgraded as the demographic warms to online video content (and other expected trends) with a screen (and other future requisites)."

But the end result would be a digestible informatic and task network instead of a multi-page sentence.

P.S. While the active voice was expressly chosen for clarity, the author of this piece reserves the ability to offer technical pontifications exceeding the standards of reputable academic journals should necessities so dictate.