9. 3. 2022
8 min read
Jozef Šulej: We make sure all ideas are validated before moving to development
Not so long ago, Jozef has taken a significant step within his career ladder by switching from a people manager to a product manager. In the interview, we talked more about the entire process, what led him to do it and what was really helpful on the way. Dig in to learn more!
Michaela Zubarova
Jozef Sulej at the office
You underwent a career change, was it a significant one? Can you explain why you made that decision?
Well yes, quite a significant one. I have only been in Product Management for more than half a year. Before that, I used to be a store manager. It was really important to me to change jobs as my previous position was mainly about risk management and problem-solving, and working with some people over there wasn't enjoyable at all. I had to do things I didn't want to and that's why I've decided to seek change. By accident, I found the Product Manager course at Sudo Academy on the internet. I checked it all out and I was immediately sure about trying it. I also have quite a lot of friends within IT, I studied at the Technical University and had some IT subjects so it's not something unknown to me. Since I haven't studied computer science and had absolutely no experience within the field I knew I wouldn't make it without a course. I somehow hoped that the course would move me forward and open opportunities.
How did the course go?
There was an introductory interview regarding my expectations and expected outcomes, not like other classic interviews. The course went quite well and I really liked it. The number of technicalities was easily bearable and understandable for a person with no previous experience. The course lasted 2 months and resulted in presentation days with companies that were partners of Sudo Academy. That's how I received an offer to go for an interview. From there it went hand in hand, I was contacted by Sudolabs in a short time and I got a job as an Associate Product Manager.
Can you say you gained full knowledge during the course?
Definitely not the full knowledge, I will probably never use that word. Theoretical knowledge? Maybe. Processes such as validation of ideas, user interviews, and the like. But those experiences are often much more than just the theory. It also doesn't always work perfectly within the framework, and you can't exactly go by those steps, therefore improvisation is important. This is where a product manager should be good at being able to come up with solutions if not everything goes according to plan.
The Product Manager should find a way to make the product successful and interesting for users.
Sudolabs' goal is to be a product-oriented company, what does that mean? What services are included?
The main idea of being a product-oriented company is to help clients validate their ideas when creating a digital product. This means not leaving it only to the developers, instead, we look at it from the perspective of who is the end-user and what we have to do in order for the product to be successful. There are agencies that skip the product part and move directly to development, at Sudolabs we make sure to avoid that and put a great focus within the product area. We are there for the client to think about the entire user experience flow and what problem it solves for the user. In Product Lab, we gradually shape the idea to a final stage to reach the point where it makes sense for the end-users. At this point, we move on to designs and development afterward. It is important for us to work only on meaningful products that are truly bringing added value to the end customer. We look at the idea from a slightly higher perspective and ensure the project can be successful.
EzTenda was your first project, can you tell us more about the project and what stages you and the client went through?
EzTenda is a startup for a digital marketplace where drink listings are tendered as a service. Given the fact it's a B2B project, the target user is not a single client, but companies, various venues, and brands within the UK.
The client and founder of EzTenda approached us with a rough business idea. There was a long journey ahead to shape this business idea into a digital product, specify who are the target users, MVP scope, long-term roadmap, etc. Our client had no previous experience with building digital products and therefore he decided to choose Sudolabs as a partner. He was the one bringing in industry expertise and it was on us to supply knowledge on how to transform a business idea into a product specification. Together we had to define how the final product would look like together with final high-fidelity designs. Founders have usually many requirements, therefore it was our job to really capture the main features. Afterward, UX flows were drawn and on their basis, the first mockups of designs were created.
What are your responsibilities during development?
During development, I hold the position of Product Owner, where I try to steer the project in such a direction, where we have a satisfied client but also we work only on those ideas and features that are necessary for the user. Every feature we choose is then iteratively validated with users to find out whether it makes sense as we created it or whether there is a need to change something. Later on, the feature is tested and we see if it has success and if it’s solving the main user problem.
Are you the person updating the client?
It's not only me but several people. At the product level, it's me and CPO Jan Koscelansky and then tech leads for the technical parts. We have several meetings planned with the client during the development sprint, such as Product Review, Product Demo, or Technical sync.
How do devs benefit from having a product manager on a project? Why is it important? What benefits does it provide them?
The main point is to make sure our developers are not working on features that are not validated and meaningful. The features have to make sense, be validated, and be approved by clients and users. As a result, it also makes more sense for developers as they know it will have added value. However it doesn't assure the feature can't change or we won't erase it completely in the next step, we're not afraid to try a new thing and change or delete it after a short period of time.
Other than that, we create roadmaps. These are created a few weeks in advance and we divide them into topics we are currently working on and topics that are just ideas for some time in the future. It's all about setting priorities. When creating these roadmap epics, every one of them is described in detail with given user acceptance criteria.
At the same time, if something is already created, it does not end there. We really try to iterate on the idea and continue testing it with users. At Product Lab, we are always improving what is already done and creating as much clarity for users as possible.
What must not lack a good product manager?
Definitely, creativity, being structured and organized. Especially when it comes to creating ideas and features. The client's idea needs to be transformed into a so-called product requirement that is thought through from beginning to end, and it is there that the client does not always think about all obstacles and possibilities. This also brings visibility to the whole team.
You are currently working intensively with devs and clients, what is the biggest challenge for you?
Time-management. I have to find time to deal with clients and also be available for developers. As part of agile development, we have various scrum ceremonies and meetings during the day, and in the meantime, I need to prepare all tasks such as roadmaps or new ideas.
It is very important that developers have all the tasks and processes written down in detail.
How to put it all together and leave nothing out is the hardest for me to deal with, especially when working on multiple projects at once.
What are your lessons learned? What surprised you the most? It's your first time in this field
One complex lesson learned is technology. On a daily basis, I learn how are SW products being developed and why we need to be careful during development. From architecture to frontend and backend. And of course, I learned a lot about various services we need to manage and set up on a project.
To my surprise, Sudolabs does not follow exactly everything the client requires. Rather than that, we bring sense to it and together with the client validate this requirement, so it is not an empty idea that may not matter to the user in the end. Sometimes you can really say no to a client and navigate him in the right direction to focus on a meaningful solution.
For how long have you been part of Sudolabs? Is there any difference compared to your old job, whether professional or personal?
It's been more than 8 months now! Certainly yes, mainly the fact I'm no longer mentally exhausted. Even though there is a lot of work, I'm able to switch off outside work and find time for myself and my own activities. My colleagues are also much more helpful, I can rely on them and they often guide me on the right path, the same way as we direct the client. Once you work on meaningful projects, the job doesn't feel like something you must do but something you truly enjoy.
What is your way of handling work-life balance?
I always try to work from the office, as procrastination can be my best friend at home. I also do some sports passively (badminton, hiking, and skiing in winter), and spend time with my girlfriend and our dog Loki. The main rule is not to work outside of the office unless it's super urgent.
What are your guilty pleasures?
Well, in my previous job, I was getting up at four in the morning. The sleep pattern I have developed since I started at Sudolabs is now quite different, as I tend to sleep longer and it's difficult for me to get out of bed, luckily I have my dog to wake me up.
You might
also like