Hi.

1st time user but been a BA for 15 years and have been using Agile Scrum & Kanban for over 5. Ive been having some blue sky thinking sessions lately to try and understand the process by which developers consume requirements and design (even in their heads) soltions. By understanding some of their processes, I hope to both improve (and simplify) this key part of my role but also to spur on developers to think differently - naybe a little more broadly - about how we can innovate by effectively utilising a different way of thinking.

When communicating with the team I wholly favour F2F conversations over boring documents but all too often see that my descriptions - even if I try and build variety into my approach - seem to foster almost immediate or automatic "go to" service components e.g. relational database, nested tables when I talk about what we want data to do for us, etc   

I was wondering if anyone has (or could point me to any reference) documents, discussions or know of advocates of ways of trying to remain technically agnostic - and as such try to prevent these "go to" solutions - when describing the what, how and why. I'm not naive and realise changing some key words probably wont break any new ground but was trying to understand perhaps more of the science of thinking at a more elementary level to try out some new ways of imparting knowledge. 

Well, until I master that Vulcan mind meld that is...