Identity and Access Management, or IAM for short, can be quite a complex topic - while the interface should strike the optimal balance between simplicity and security, making sure 'the parts work' is quite an intricate affair.

Going from an initial idea to the first publicly available version of a mobile app requires a multitude of steps, which are covered in this case study: starting with discovery efforts such as research and prototyping, over into alpha builds, closed and open betas all the way to invite-only and open public releases.

Hiring product managers is particularly difficult because interviewing them is mostly a test of soft skills. Sitting in the interviewer's chair and conducting over 30 interviews as a client service, I was able to notice quite an amount of interesting aspects that may also be helpful for anyone in the process of getting a job or a hire.

In this case, we were looking at the other side of app-related fraud prevention - possibly fraudulent activities connected to the app, but happening outside of it. This especially relates to logins & accounts being compromised, as well as attempted scamming/phishing attempts.

Employing various methods of doing urgent and strategic fraud prevention, we secured two different apps from different potential exploitations, ranging from payment-related fraud to fake user engagement and crediting.

By doing product discovery work on a tourism and travel client’s business and product strategy, we were able to uncover necessary structural changes to their offering and develop a plan for implementation.

In spite of the drawbacks of an OKR-based strategic environment, the team and I managed to complete an important project within one quarter’s time that had typically been left behind — for far too long.

To validate investing time in building a collision detection feature into a messaging app, we used a very simple prototype  showing collision  to confirm validity of our approach and justify investing more resources into it. Continue reading here…