Articles by Daniel Heo-Lu
- OKRs for Platform Work
Some Daniel's key things covered include: • For platform work, OKRs that measure progress in milestones over 2-3 month periods within a quarter can be effective. • Measuring the time it takes to complete typical tasks before and after the new APIs are built can be a goal, aiming for a 20% reduction in completion time. • Having architectural designs completed and approved by certain dates can be an OKR milestone. • Getting feedback from internal teams early on can show if the work is positively impacting them. • The number of available endpoints can be counted as progress towards KRs. • Adoption KRs can track the number of teams starting to use the new APIs. • Usage KRs can measure the % of new APIs used over old APIs or the volume of API traffic. • Any business impact or revenue enabled by the work can be captured. • Performance, security, extensibility and maturity of the APIs can be graded on a scale and improved over time. • Having multiple senior engineers independently grade the APIs can help resolve discrepancies.