The story of Feynman started within a Property Management firm. Rather than researching user needs first, they jumped straight into building an internal tool. While this approach gave them initial momentum, it created significant challenges later on.
Their engineers had to take on the role of UX designers, spending valuable development time figuring out user flows. The result was a dated interface with inconsistent design patterns that confused users as they navigated different parts of the platform. This lack of proper UX planning hampered the engineering team, slowing development and making new feature implementation unnecessarily complex. As a result, development costs increased while team motivation declined.
The team made a smart decision to pause development. With me on board, we evaluated their existing product to identify the most critical UX and product issues.
Armed with a clear understanding of the problems, we began developing an improved version. This time, we prioritized building a comprehensive design system—a library of reusable components and patterns. This foundation would enable the team to develop new features more efficiently and consistently, avoiding the design inconsistencies that had plagued the original version.
