Darwin Sanoy

Learn how to differentiate Solution Engineering and Product Engineering. They are similar, but different in key areas such as "Justification to Build", "User Engagement", "Timelines", "Time to Value", "Who To Solve For", "What to Build With", "Who Maintains The Outputs" and many other factors. Both play critical roles in the the entire technology ecosystem at any software company. Topics: 1 Differentiate the fundamental differences between Solution Engineering and Product Engineering. 2 Understand which customer requests are appropriate for either or both of these types of Engineering. 3 Discovery process for improved Solution Engineering.

This sessions articulates and demonstrates how aligning tooling with known habit formation approaches is an accelerator as it: • Fundamentally aligns with positive human habit psychology research. • Precisely inserts process automation innovations in existing workflows. • Gives critical "rich context" to tap into existing motivations to voluntarily do the right thing. • Facilitates the fundamental human need for low friction collaboration.  When we try to transform security practice into business as usual habits, we need the above list to be precisely tuned - your DevSecOps solution be built to do the same.

Do you find yourself constantly re-mixing the same how to content for a new audience and saving it as a new deliverable? Have you ever wondered if there is a more efficient way to reuse your enablement content? Learn the basics of making how to content that can be leveraged over and over with minimal adaptation to multiply the impact of sharing your expertise. You can make a HECA-of-a-good how-to with the Hyperscaling Enablement Content Architecture.