FusionTalk

In this episode, Anouck and Steve kick things off by exploring the concept of brainstorming. Moving on from their initial discussion, they delve into the intriguing question: Is collaboration merely communication with a goal?

They examine how collaboration integrates into communication strategies and discuss whether any straightforward, linear processes enhance communication through collaboration. And yes, they do get stuck a little on how much of the process is brainstorming... agreement is not forthcoming in this episode... maybe in the next episode we will have a consensus

Tune in to discover their insights and conclusions on whether collaboration is fundamentally communication aimed at achieving specific goals.

Welcome to FusionTalk, where your hosts Steve and Anouck unlock the secrets and strategies behind effective mind mapping. In today's episode, we delve into the fundamentals of ‘what a mind map is’ and its transformative potential as a tool for clarity and organization. But that's just the beginning. We'll explore why incorporating mind mapping into your routine can be a game-changer, especially when bridging the gap between business and IT departments.

Through engaging discussions and expert insights, we discover how mind maps can serve as a dynamic communication tool, fostering understanding and collaboration across disciplines.

Furthermore, we'll discuss how leveraging mind maps in meetings can revolutionize your note-taking process, making information accessible and understandable for everyone involved.

Join us as we navigate the versatile world of mind mapping, proving that it's not just a tool for the few, but a skill that can benefit everyone. Stay tuned as we map the path to more transparent communication and streamlined thought processes.

We talk about the book of Tony Buzan – Use your head. It’s worth reading; it will give you insides into mind mapping and other tools to use your brain more efficiently.

In this podcast, Steve and Anouck engage in a thought-provoking discussion on whether companies should buy software or develop it themselves. Steve opens the conversation with strong arguments in favor of buying software. He points out the immediate access companies gain to their needed tools and the ease with which they can stay updated, always running the latest versions thanks to automatic updates.

As promised here is the IT Depends link https://www.youtube.com/@ITDependsSteve

On the other side of the debate, Anouck presents a compelling case for in-house development. She emphasizes the unmatched benefit of customizing software to meet exact business requirements and the invaluable accumulation of knowledge within the company that comes from developing software internally.

As the conversation unfolds, the core question emerges: Which approach, buying or developing, is superior? The answer, they suggest, hinges on the specific needs and strategic goals of your business. Tune in to discover who comes out on top in this insightful exploration of aligning technology decisions with business requirements.

After shouting out on the community, we met at Bremen, Anouck, and Steve. Mentions to the people we met and the people we missed. Cool ideas around Minecraft as a change tool with Gamification.

Eventually, the subject at hand is discussed, and how IT and business need to be aligned more on how business units and IT should be working together. Lots of ideas discussed: Speed dating, gaming nights, a little competition to give people... who knows where this might turn up.

The discussion looks deeper at how IT and Business need to get closer and bring additional value to the company simply by working as a unit on each application or value items that benefit the company.

Have you ever been involved in a project and felt like you were going around in circles and not moving forward... well Anouck has a solution “Kill it or be Killed” Listen to Anouck and Steve as they describe the situation where no solution appears to work... so...

This podcast looks at the process of being blocked, stuck and unable to move forward. How it feels and when a drastic solution is needed, throw it away and start again.

Using a real-world example of a connected workflow drawing content from a remote system, we look at the process around making the decision to stop, re-think and re-design the code to something more efficient (quicker) simplified with a focus on the goal and finding the courage to accept that “I have learned little” from the direction I was moving in and needed to return to Point A and take a different route to success.