Michael Tuason / Design Portfolio

Designing Systems for Decisions Under Constraints

 

Hi, I’m Mike. I design systems where people make decisions with limited time, incomplete information, and real consequences when things go wrong.

 

Over the past 8+ years at Amazon and TIBCO, I’ve worked on scheduling, livestream, and order fulfillment platforms where system behavior directly impacts operations. I focus on making that behavior clear so users understand what’s happening, why it’s happening, and what to do next.

 

My background in Computer Science helps me work closely with Product and Engineering in deciding what to build, defining system logic, and making tradeoffs early to avoid bigger issues later. And by synthesizing stakeholder feedback, I’m able to bring clarity of the user problem to the team.

 

 

What I Do Best

 

  • Decision-heavy systems - where rules, constraints, and edge cases drive outcomes

 

  • Complex workflows - shifting decisions earlier to prevent downstream errors

 

  • Real-time platforms - where timing, coordination, and reliability matter

 

  • System behavior - making “why things happen” visible in the UI

 

 

What’s Different About How I Work

 

I make the complexity visible in a way users can actually work with. That usually means:

 

  • defining system states early

 

  • exposing constraints instead of masking them

 

  • shifting decisions earlier in the workflow

 

  • designing for failure cases, not just ideal flows

 

The result is systems that are more predictable, easier to operate, and less likely to fail when it matters.

Michael Tuason / Design Portfolio

Designing Systems for Decisions Under Constraints

 

Hi, I’m Mike. I design systems where people make decisions with limited time, incomplete information, and real consequences when things go wrong.

 

Over the past 8+ years at Amazon and TIBCO, I’ve worked on scheduling, livestream, and order fulfillment platforms where system behavior directly impacts operations. I focus on making that behavior clear so users understand what’s happening, why it’s happening, and what to do next.

 

My background in Computer Science helps me work closely with Product and Engineering in deciding what to build, defining system logic, and making tradeoffs early to avoid bigger issues later. And by synthesizing stakeholder feedback, I’m able to bring clarity of the user problem to the team.

 

 

What I Do Best

 

  • Decision-heavy systems - where rules, constraints, and edge cases drive outcomes

 

  • Complex workflows - shifting decisions earlier to prevent downstream errors

 

  • Real-time platforms - where timing, coordination, and reliability matter

 

  • System behavior - making “why things happen” visible in the UI

 

 

What’s Different About How I Work

 

I make the complexity visible in a way users can actually work with. That usually means:

 

  • defining system states early

 

  • exposing constraints instead of masking them

 

  • shifting decisions earlier in the workflow

 

  • designing for failure cases, not just ideal flows

 

The result is systems that are more predictable, easier to operate, and less likely to fail when it matters.

 

 

 

 

Michael Tuason / Design Portfolio

Designing Systems for Decisions Under Constraints

 

Hi, I’m Mike. I design systems where people make decisions with limited time, incomplete information, and real consequences when things go wrong.

 

Over the past 8+ years at Amazon and TIBCO, I’ve worked on scheduling, livestream, and order fulfillment platforms where system behavior directly impacts operations. I focus on making that behavior clear so users understand what’s happening, why it’s happening, and what to do next.

 

My background in Computer Science helps me work closely with Product and Engineering in deciding what to build, defining system logic, and making tradeoffs early to avoid bigger issues later. And by synthesizing stakeholder feedback, I’m able to bring clarity of the user problem to the team.

 

 

What I Do Best

 

  • Decision-heavy systems - where rules, constraints, and edge cases drive outcomes

 

  • Complex workflows - shifting decisions earlier to prevent downstream errors

 

  • Real-time platforms - where timing, coordination, and reliability matter

 

  • System behavior - making “why things happen” visible in the UI

 

 

What’s Different About How I Work

 

I make the complexity visible in a way users can actually work with. That usually means:

 

  • defining system states early

 

  • exposing constraints instead of masking them

 

  • shifting decisions earlier in the workflow

 

  • designing for failure cases, not just ideal flows

 

The result is systems that are more predictable, easier to operate, and less likely to fail when it matters.