Designing a complex Leasing software

We will discuss about Keshavarzi’s leasing system designing process here. What were challenges and what we achieved.

Where does the story begin?

An example of how one of leasing steps works as business model

How did we start?

  • We only had one product in country which was similar to ours’s so we didn’t have many examples to do deep research and competitive analysis
  • This system was new for us. We didn’t have any experience with leasing process in real world and now we have to design it!
  • The whole system was considered to have multiple users and panels. By saying multiple users, I mean every single request of users should transfer between different panels with different admins and that’s hard! (You can easily understand what I mean using the picture above)
  • Leasing process was happening in traditional way in the country. For every step, there were many paper works and different difficulties. We didn’t know the exact concerns of this world and also how to make an online clone of it.

What we needed

Time to start

Overall view of what we needed for our documentation system

Process of work

It was a total chaos but we’ve managed that situation with huge documentation. We documented every action and decision we made for each screen and each field. Speaking of documentation, It’s worth to mention that each step of leasing process has made of different subsets and each subset had it’s own components. That’s where we decided to do everything specially our documentation process in atomic way. Because as I mentioned, everything was so complex and huge. By doing this way of documentation and design, now changing every part or any further actions was much easier and simple. We were almost faster this way!
As I mentioned, we were learning during designing process about leasing. So we’ve decided to put anything that we learn about each part in it’s document so we made it impossible to forget about them and also everything would be clear for other designers and other teams.
Another matter was the system’s integration. Each panel had it’s own rules and functions but overall they were making a single product together. It was important to keep everything integrated. We didn’t have much time to create some general rules for our design structure and that’s why we’ve decided to design everything and then redesign everything again once we got to the end. It was much faster and also accurate; because we had experienced the whole process once and we knew about similar parameters. Now we were able to create some great general rules based on real data and experience to refactor everything.

Let’s do some test

One of the screens of our work-flow that we designed

What we learned?

Product Designer at Digikala and MCI.