Error and exception

Services are dynamic by nature. Things come together to make good things happen. As and when they do, they may throw errors and exceptions. Good design must account for such possibilities, and that means some dialog and interaction will be necessary between users and agents. This is the part that often creates stress and strain between the two sides, and how well it is handled is often critical to the design of a service. Contracts and agreements have a certain level of flexibility and tolerance, and how much often depends on funding and payments.

Filed under: principles


TL;DR I can audit the design of a service to prevent or predict systemic failure, using a proprietary method called 16F I make intractable problems, tractable by reframing them. I then design solutions that won't create problems elsewhere, now or in the future. The solutions are in the form of services. I focus on system-level structures that give meaning and purpose to the design of lower-level constructs such as processes, interfaces, and interactions. I've spent the last 10 years obsessed with the questions: What are services? Why do they fail? Why do they exist? I'm now writing a book. Design is my dogma. Curiosity is my doctrine. Industrial engineering is my discipline. @mxiqbal

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s