RT
@saurabhsoni_ss: 𝟱𝟬𝟬+ 𝗣𝗥𝘀 𝗺𝗲𝗿𝗴𝗲𝗱 𝗯𝘆 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗿𝘀! ~70% of them are core product and feature work, rest bug fixes and maintenance. 𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 𝗺𝘆 𝗻𝗼𝘁𝗲𝘀.
Design is now a very different function at
@Razorpay. Product designers don't just own mocks, they own the actual experience in production, designing, building and maintaining it.
6 months back, we decided to revamp how we build software. A big part was design handoffs: an unnecessary collaboration tax in today's world. With the right context and skills, AI can now write great code. So, anyone should be able to build.
So, we reworked our engineering systems and design workflows. We experimented a lot, made some mistakes too, and built an org where shipping is part of every product designer's job.
𝗪𝗵𝗮𝘁'𝘀 𝗼𝘂𝗿 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄? That's a long answer for here. If you're interested, lmk in the replies and if enough folks are keen, we'd love to do a presentation or video on it!
----------------
𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗜 𝗸𝗲𝗲𝗽 𝗴𝗲𝘁𝘁𝗶𝗻𝗴:
𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗱𝗼𝗶𝗻𝗴 𝘁𝗵𝗲𝗻?
Building the systems that let everyone in the org build at scale: Our in-house coding harness, PR review automation, CI/CD automation, and a lot more.
𝗛𝗼𝘄 𝗱𝗶𝗱 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗿𝘀 𝗹𝗲𝗮𝗿𝗻 𝘁𝗼 𝗰𝗼𝗱𝗲?
They didn't have to learn to code. They learnt the foundations of engineering, thinking like an engineer. It happened through learning sessions and on the job.
𝗔𝗿𝗲 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗿𝘀 𝗳𝗿𝗼𝗺 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱𝘀?
Some are. Many aren't. We've built a team of generalist designers who are keen to learn anything.
𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗻𝗲𝘄 𝗿𝗼𝗹𝗲𝘀? There are two:
1. Design Builders: designers who own the production experience.
2. Design AI Engineers: folks who build the systems and workflows that let designers ship.
𝗗𝗲𝘀𝗶𝗴𝗻 𝗕𝘂𝗶𝗹𝗱𝗲𝗿 𝘃𝘀 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗗𝗲𝘀𝗶𝗴𝗻𝗲𝗿?
A Design Builder is a very different role from a typical design role. They truly own the production UI, UX, interactions, performance, bugs and quality, in code.
Huge shoutout to the entire
@Razorpay_Design team! You took this up, pushed yourselves into a completely new world, took insane ownership and made it happen. 🙇♂️