Challenge 4: Why I saw system limits as an advantage, not a problem

System constraints are not the opposite of good design. Instead, they are the rules of the game, and solving well within the rules is how we earn real excitement.

Muaban's architectural limits meant both teams were already operating inside the same boundaries, which became the condition for prioritization. Rather than handing over a list of recommendations, I proposed joint HMW sessions where both teams framed gaps as open questions together, making their PMs co-authors of the problem instead of defenders of the existing system. Additionally, we used the 10 Usability Heuristics to ground the UX case and the Hooked model to explain the behavioral logic.

Obviously, architectural limits became the criteria we used to align on priorities, turning the constraint into the structure that kept the work coordinated.