Many times, we’ve seen organizations with particularly complex domains fail in their modernization efforts. To be successful, we need to have a firm grasp on the domain and the relationships to other systems and domains. But most importantly, we need to put the people who are using our systems at the center of our problem solving.
When we only use an engineering lens to design our systems, we don’t always get enough perspective to make sure we’re building the right thing. Are you asking the right questions? Are you anchoring your architecture to the wrong needs? Is your decision-making influenced by assumptions and biases?
Without a holistic understanding of how each component of your system is (or isn’t) meeting the needs of your users— no matter how well your systems are architected, you risk having critical gaps in your design and strategy. You risk not being able to deliver value for your users.
Olivia’s product design background and Indu’s software architecture background bring a set of methods that will help you look at the complexity and make sense of the mess in a structured, repeatable way. We’ll expand your toolbox of (remote-friendly) collaborative, cross-disciplinary techniques to understand your domain and center the people that your systems serve.
indualagarsamy
kmwebnet
soracom
guchey
colopl
sansantech
dahatake
cheng_wei_chen
hankehly
oracle4engineer
unclejoe
whywaita
ymotongpoo
mraible
chriscoyier
addyosmani
aki_iinuma
colly
sachag
phodgson
jcasabona
frogandcode
keavy
chrislema
samanthasiow