How to influence without authority

#52 – August 30, 2021


A common concern for programmers considering low-code tools is the lack of flexibility when faced with complex requirements. Linx, a general-purpose development tool, follows a programming paradigm that makes it easy for developers and IT professionals to pick up. They use it to build highly customised, APIs and integrations, faster, using bigger, prebuilt pieces, with visual help, and lots of ready-made functionality available on the server-side.

this week's favorite

As a Product Manager, you are working within a discipline that exists at the intersection of many other functions (design, engineering, analytics, marketing, finance, etc), but rarely have these disciplines directly reporting to you. Being able to influence all these simultaneously is not an easy task, but a necessary one in order to drive outcomes for your customers and the business you work for.

Once an incident is resolved, there is a tendency to move on and go back to normal daily work. This is a missed opportunity to gather critical learnings and understand true system behavior as well as process and system breakdowns.

Best practices aren’t universal and the use of the term without deeper consideration can be problematic. They’re straightforward, simplistic answers to difficult questions. Quick answers can at times work in our favor, a way to avoid cognitive overhead and set a clear path to a solution.

Whether it was our first call or our hundredth, founders inevitably asked me whether they should market and sell their enterprise software to buyers/executives (top-down) or to users (bottom-up).

It breathes life into your engineering team, and teams across the company, as customer issues and requests are resolved quickly and efficiently. But here’s the caveat: you can’t just ship fast, you have to make sure your team is equipped to ship safely.