Designing for the Unknown

 

I've had to work on several projects for hardware that was still being built and operating systems that were not finalized. The concept and design had to be completed before the hardware launched so we would have a product ready they were ready to ship. Designing for so many unknowns was easily the most challenging project I've ever tackled. 

We needed to create a seamless experience without knowing how the clerk would be entering Perka or even what data would be available to us. 

I think of it like building a house of cards. Just one misaligned element and your house crumbles. The challenge for me was building that house with a simple but strong central structure that would remain unaffected when half of my cards were removed. This is an MVP product and not terribly demanding in complexity. Our challenge was building something that could was basic enough that it could easily be disassembled and tweaked. Perka's integration with the Clover platform needed to solve the problem of validating a transaction regardless of if the customer was paying cash or credit from non-clover register. Because we couldnt know if our system would have any knowledge of the transaction from whatever point of sale terminal the merchant might be using we had to plan for the worse and trim back whatever would not be needed.

 An early task flow with an adaptive experience depending on whether or not the validator would have knowledge of the order total, inventory, etc.

An early task flow with an adaptive experience depending on whether or not the validator would have knowledge of the order total, inventory, etc.


UI Examples