Session + Live Q&A
Talk Like a Suit: Making a Business Case for Engineering Work
We all know the feeling. We see these scary problems in our code and architecture, we raise our concerns, leadership nods their head encouragingly, but every planning session and backlog grooming, only features show up on the list. You think, well, I guess we'll have to wait for something horrible to happen, and then finally they'll be motivated. This can be frustrating and discouraging; you want to do the right thing for the company and avoid disaster, but nobody seems to be listening.
Being able to "talk like a suit" - make a compelling business case for engineering work - is a key skill we need to learn as we grow in our career. Over the years I have learned some great strategies for doing this. I have found when I work to make a solid business case, I become even more convinced and confident that what I've been worried about is a real issue, or, sometimes, I realize that the investment needed just isn't worth it for the value it will bring.
In this talk I'll walk through some of the approaches and strategies I use to make a business case, and will walk through a few examples to help make it concrete. You should hopefully walk away with your own ideas on how you can reframe the problems you're trying to fix in business terms, and feel more confident that you can make a larger positive impact for your organization.
Speaker

David Van Couvering
Senior Principal Architect @eBay
David Van Couvering has been designing, building and delivering enterprise software since he first started at Sybase in 1988, converting tests from C to COBOL. His checkered past includes architecting one of the first Java application servers at Sybase, working on a series of explosively failing...
Read moreFind David Van Couvering at:
From the same track
Analyzing Codebases for Fun and Profit
Tuesday Nov 2 / 12:10PM EDT
One problem existing for many developers today is ramping up quickly complex and sometimes messy codebases. Analyzing domains is an important skill when we need to solve complex problems, take ownership, contribute to open source, break down monoliths, or even perform code reviews in unknown...

Jordan Bragg
Architect @CastlightHealth
Creating an Atmosphere of Psychological Safety
Tuesday Nov 2 / 01:10PM EDT
Psychological safety is being able to show and employ one’s self without fear of negative consequences of self-image, status, or career. Psychological safety can be defined as a shared belief that the team is safe for interpersonal risk-taking. In psychologically safe teams, team members...

Tim Berglund
Senior Director of Developer Experience @Confluent
Becoming a Better Developer Panel
Tuesday Nov 2 / 03:10PM EDT
In this panel, we'll discuss ways to improve as developers. Are better tools the solution or can simple changes in mindset help be a more effective developer as well as a better team player? And what practices are already here but not yet universally adopted?

Jordan Bragg
Architect @CastlightHealth

David Van Couvering
Senior Principal Architect @eBay

Dave Copeland
CTO @mood_health