đ Going back to school, I was featured in The Decision Intelligence Lab podcast, and Product OR Engineers
Local Optimum: short, imperfect-yet-useful ideas - Edition #20
Welcome to a new edition of Local Optimum: a short, imperfect-yet-useful collection of ideas related to optimization, decision-making, and applied Operations Research.
Letâs dive in! đȘ
1) đ Going back to school
September is traditionally the month of going back to schoolâŠ
And here I am! :-)
One of the first things I did was to upgrade the Notion database with Operations Research resources adding an entire new section: use cases.
Theyâre useful to find inspiration from similar problems, industries, or tools.
Here you can find my announcement.
Iâd also like to take advantage of this publication to say a big THANK YOU if you subscribed during August (considering I didnât write any. single. post).
Literally, dozens of you subscribed during this past month:
Most probably, you did it because I appeared in one of my favorite podcasts.
And speaking about thatâŠ
2) đ» I was featured in The Decision Intelligence Lab podcast
I didnât write any single word here.
Yet I appeared in one of my favorite podcasts: The Decision Intelligence Lab podcast.
Vijay, Mike and I talked aboutâŠ
Not developing for your users.
The importance of testing your optimization models.
And where to start when automating decisions at any business.
(among other things)
I encourage you to subscribe to the podcast here:
And why did I appear there? Well, Vijay found my ideas around the Product OR Engineer role powerful đđ»
3) đ Product OR Engineers
Algorithms, mathematics, chasing optimal solutionsâŠ
Thatâs what academia teaches us.
But thatâs a small part of our work to deliver value to the business. What if your focus is onâŠ
đŻ Having a business impact mindset.
đ„ Owning problems, not just models.
âïž Balance optimality with usability.
đ§âđ€âđ§ Build with users, not for them.
All of that, together with writing good software, is what you need to succeed in more integrated roles within organizations.
This shift reflects the transformation in software development, where engineers are taking on responsibilities traditionally held by product managers.
Continue reading here:
A proof of the Product OR Engineer role
Next Monday, Iâll share something I saw during August: a role thatâs speaking directly to those who want to make a real impact.
Itâs important because I talked about the Product OR Engineer role back in April, and now itâs materializing into job offers.
Iâll dissect the job offer for you so that youâre able to identify and match its requirements with the ideal candidate.
If you want to see the role of the future, this will be useful. See you Monday!
And thatâs it for today!
If youâre finding this newsletter valuable, consider doing any of these:
1) đ Subscribe to the full version: if you arenât already, consider becoming a paid subscriber. Youâll get access to the full archive, a private chat group, and 30% off new products.
2) đ€đ» Collaborate with Feasible. Iâm always looking for great products and services that I can recommend to subscribers. Also, if you want to write an article with me, Iâm open to that! If you are interested in reaching an audience of Operations Research Engineers, you may want to do that here.
3) đ€ Share the newsletter with a friend, and earn rewards in compensation. Youâre just one referral away from getting The Modern OR Engineer Playbook: Mindset, methods, and metrics to deliver Optimization that matters.
If you have any comments or feedback, just respond to this email!
Have a nice day ahead âïž
Borja.
