Dan Timpson

Everyone wants to be more "proactive" and less "reactive," but it's hard to predict how traffic patterns will evolve or how increased utilization in one service might impact other services. Check out this article from Endre Sara for what to consider when trying to build more resilient applications.

29

1 Comment

When Kevin Coleman and I started Ravenna, one of the first things we did was sit down with Ops leaders and ask one simple question: where does your team actually work❓ The answer wasn’t a portal. It wasn’t some legacy dashboard with its own login, training module, and adoption curve... It was Slack. Teams. In Slack and Teams, HR managers answer questions about benefits and PTO. IT directors reset passwords, unlock accounts, and ship out new laptops. Operations teams track down approvals, chase missing data, and route requests across departments. That’s where the real work piles up, and where it needs to be automated. The incumbents technically “integrate” with chat, but the pattern is backwards. Their apps use Slack as a notification layer, just to push you back into their portal. That anti-pattern is what kills adoption. People don’t want to leave the environment where they’re already working. The fix is obvious: keep the work in chat, not in a portal. Ravenna lives entirely inside Slack/Teams. The bot handles requests in-line, so the problem is solved where the conversation starts. Need a new laptop? Submit the request in Slack, and it’s approved and ordered without leaving the thread. Locked out of Salesforce? Ask in Teams, and the bot helps you restore access quickly. Looking for the PTO policy? The exact page from the handbook surfaces right where you asked. Ravenna is designed for convenience on purpose, but the real outcome is adoption. Drop a separate portal in front of employees, and usage falls off a cliff. Keep the workflow in Slack or Teams, and people actually use it. That’s where you capture the signals: who’s asking for new laptops, who needs Salesforce access, who’s stuck on an HR policy. And once you capture those signals, you can automate the repetitive requests that eat up time. This is the philosophy we’re betting on: co-location beats portals every time 🚀

34

1 Comment

Navigating Between Technical and Non-Technical Worlds? Is "user-friendly" really about adding another feature, or is it about removing distractions? Connecting technical and non-technical teams involves translating not just words, but intentions and priorities. This might sound easy, but trust me—it’s an art form. The right approach? Listen before you speak, simplify without condescending, and always stay curious. Think of yourself as a translator: not just for words, but for mindsets. When both sides feel heard, collaboration becomes second nature.   #Leadership #Collaboration #QA #Management #Mentorship

62

2 Comments

Every team I meet has its own definition of "platform engineering." Some see it as a collection of tools. Others see it as a team. A few are starting to see it as a discipline. My take: Platform engineering is a shift in responsibility. From humans managing tools, to systems managing complexity. That shift is just beginning. Read Why Platform Teams Need Systems That Understand, Not Just Execute → https://lnkd.in/g_5dKWXa #kubernetes #devtron

30

Given the number of hours we work day in and day out to deliver quality software as software testers, sometimes we delete a process by mistake, and this is quite normal. Look no more: Did you know that you can restore a deleted process from Worksoft Certify with just a few clicks? What's more: Worksoft Certify gives you an intuitive option to customize and look for all the processes you may have previously deleted. Check out the short video to see this in action. #Worksoft #WorksoftCertify #TestAutomation https://lnkd.in/gpCCx3fB

34

What does it actually look like to lead a 300-person software org inside a 1,000-person company and still stay focused on people first? Brendan Wovchko, CTO at Ramsey Solutions, joins Scott Dunn on episode 146 of the Agile Mentors Podcast to talk about what it really takes to lead Agile teams inside a large, fast-moving organization. From developing leadership habits to navigating team dynamics and staying grounded in purpose, this conversation is full of thoughtful takeaways for anyone working at the intersection of people, process, and product. You can listen to the episode wherever you get your podcasts or get it directly on Spotify here: https://lnkd.in/gwJmrPnd

22

4 Comments