In digital landscape user experience is paramount and organisations must ensure their applications and systems are functioning optimally at all times. Traditional testing and monitoring practices have long been relied upon to achieve this goal. However, the line between testing and monitoring is becoming increasingly blurred with the emergence of synthetic monitoring.
For big data and complex data processing, data pipelines have emerged as a popular solution for managing and manipulating data. They provide a systematic approach to extract, transform, and load (ETL) data from various sources, enabling organizations to derive valuable insights. However, as with any technology trend, data pipelines have not been immune to misuse and overuse.
Ability to think critically and anticipate potential problems is essential for success for product management. One mental model that can greatly aid product managers in this regard is inversion. Inversion, a concept popularized by the German mathematician Carl Jacobi, involves thinking about a problem in reverse order or considering the opposite of what is desired.
It seriously turns me off when organisations are unable to differentiate between a role and a job. Talking about this confusion, Scrum Product Owner probably one of the most misunderstood roles these days which unfortunately many organisations advertise as a job. A job describes what one does daily. A role encompasses how our actions help an organisation to succeed. Next time you are not sure, ask yourself how you add value to the organisation.
What can we learn from Cyberpunk 2077’s disastrous launch? Cyberpunk 2077 was extensively advertised yet highly buggy release. Sony has pulled Cyberpunk 2077 from its PlayStation store following widespread complaints about glitches. The game lost over 75% of players on Steam. The stock value of CD Projekt Red (CDPR) - Developer of Cyberpunk 2077 - is down by 50%. CDPR board and management are now defensive as they now face hostile staff (i.e.
Organizational debt is a sibling of technical debt. While technical debt is unhealthy and generally a well-understood problem, organizational debt can be killer and often treated as an afterthought.
I am thrilled to announce the early availability of Axioms - a financial-grade identity and trust management platform. Axioms enables organizations to protect their apps, devices, and APIs against unauthorized and untrusted access using our fully-managed SaaS offering.
The evolution of your technology architecture should depend on the size, culture, and skill set of your engineering organization. In fact, they should coevolve. There are no hard-and-fast rules to figure out interdependency between technology architecture and engineering organization but below is what I think can really work well for a typical product startup.
When hiring for senior roles, companies put too much stress on stakeholder management skills i.e. ability to navigate through complex stakeholder landscape and manage expectations. I find the ability to form meaningful and impactful partnership a lot more important skill than stakeholdership.
When it comes to organising engineering teams, a popular view has been to organise your teams based on either Spotify’s agile model (i.e. squads, chapters, tribes, and guilds) or simply follow Amazon’s two-pizza team model.
When it comes to agile estimation, quite often agile teams spend a big chunk of their time in heavyweight processes like detailed story point estimation to improve the predictability or accuracy of their estimates. In other words, agile teams invest more time in estimation to reduce that variance (i.e. time estimated vs. time taken) which otherwise can be used to create features and add business value.