Wall of love for Brainlabs Digital
We hosted a hackathon in collaboration with Google Cloud.
The event surpassed all my expectations and I was blown away by the calibre of what was produced over the 2 days.
A big shout out to my amazing engineering team and a special thank you to Sophia Lee, Jonny O'Connell, Yen Chau + Deb Lee.
We hosted a hackathon in collaboration with Google Cloud.
The event surpassed all my expectations and I was blown away by the calibre of what was produced over the 2 days.
A big shout out to my amazing engineering team and a special thank you to Sophia Lee, Jonny O'Connell, Yen Chau + Deb Lee.
Extremely productive week at Brainlabs India. Great to catch up with the team in Bangalore and experience Onam Sadhya. Thank you for your hospitality.
#Brainlabsindia
#Brainlabs
Extremely productive week at Brainlabs India. Great to catch up with the team in Bangalore and experience Onam Sadhya. Thank you for your hospitality.
#Brainlabsindia
#Brainlabs
I’m delighted to share my promotion to Global CTO at Brainlabs.
After almost nine years of building and scaling our unique technology offering, I’m honoured to take on this new challenge.
I’m incredibly proud of what we’ve accomplished together. We’ve built a world-class engineering team and developed innovative solutions that have driven significant growth and success.
I’m looking forward to leading our global engineering team to new heights. We’ll continue to push the boundaries of digital marketing technology and deliver exceptional results for our clients at Brainlabs, the High-Performance agency.
#brainlabs
#cto
#techleadership
#digitalmarketing
#innovation
I’m delighted to share my promotion to Global CTO at Brainlabs.
After almost nine years of building and scaling our unique technology offering, I’m honoured to take on this new challenge.
I’m incredibly proud of what we’ve accomplished together. We’ve built a world-class engineering team and developed innovative solutions that have driven significant growth and success.
I’m looking forward to leading our global engineering team to new heights. We’ll continue to push the boundaries of digital marketing technology and deliver exceptional results for our clients at Brainlabs, the High-Performance agency.
#brainlabs
#cto
#techleadership
#digitalmarketing
#innovation
From Coder to Coach: My Transition to Leadership
I've always been a hands-on problem solver. My early days in development ingrained in me the satisfaction of crafting solutions and seeing code come to life. However, as my career progressed, I found myself drawn to leadership roles, a transition that wasn't without its challenges.
Initially, the shift from individual contributor to manager was daunting. I longed for the tangible results of coding but I soon realized that by leading a team, I could amplify the impact. With a large team of developers, I could potentially deliver X times the work. The key was to empower my team, fostering their growth and encouraging them to take ownership of their projects.
Today, I derive immense satisfaction from coaching teams to excel and seeing them deliver exceptional products. While the individual contributions are important, the collective success of the team is ultimately what matters most.
The transition requires a significant mindset shift. It's about balancing the desire to dive into the code with the need to oversee the bigger picture. As a leader, I've learned to think strategically, delegate effectively, and create an environment where my team can thrive.
While I still enjoy the occasional coding session, my primary role is to guide and support the engineering team. I shield them from distractions, provide mentorship and create opportunities for growth. By empowering the team, I'm not just managing a group of individuals; I'm building a high-performing unit that can achieve extraordinary things.
Brainlabs
#CTO
#Techleadership
#Digitalmarketing
#innovation
From Coder to Coach: My Transition to Leadership
I've always been a hands-on problem solver. My early days in development ingrained in me the satisfaction of crafting solutions and seeing code come to life. However, as my career progressed, I found myself drawn to leadership roles, a transition that wasn't without its challenges.
Initially, the shift from individual contributor to manager was daunting. I longed for the tangible results of coding but I soon realized that by leading a team, I could amplify the impact. With a large team of developers, I could potentially deliver X times the work. The key was to empower my team, fostering their growth and encouraging them to take ownership of their projects.
Today, I derive immense satisfaction from coaching teams to excel and seeing them deliver exceptional products. While the individual contributions are important, the collective success of the team is ultimately what matters most.
The transition requires a significant mindset shift. It's about balancing the desire to dive into the code with the need to oversee the bigger picture. As a leader, I've learned to think strategically, delegate effectively, and create an environment where my team can thrive.
While I still enjoy the occasional coding session, my primary role is to guide and support the engineering team. I shield them from distractions, provide mentorship and create opportunities for growth. By empowering the team, I'm not just managing a group of individuals; I'm building a high-performing unit that can achieve extraordinary things.
Brainlabs
#CTO
#Techleadership
#Digitalmarketing
#innovation
Zuckerberg’s Controversial 2025 Prediction
Mark Zuckerberg's recent statement about AI replacing mid-level engineers by the end of 2025 is certainly headline grabbing and sparks important discussion. It's a bold claim and while I acknowledge the rapid advancements in AI, particularly in coding and software development, I believe the reality is much more nuanced.
AI is undoubtedly becoming an increasingly powerful tool. We're already seeing AI automate certain development tasks, boosting developer efficiency. However, software engineering is a multifaceted discipline. Beyond coding, it involves understanding user needs, complex problem-solving, system design, and crucially, collaboration. While AI can excel at specific coding tasks, these broader responsibilities require human judgment, creativity and strong communication skills—areas where humans still have the advantage in 2025.
Mid-level engineers play a vital role in our teams. They tackle complex projects, often lead smaller teams, and mentor junior engineers. AI can undoubtedly assist with these tasks, but I foresee it being a valuable support tool rather than a complete replacement in the near future. I believe we'll see AI empowering our engineers even more, making them more productive and efficient, and allowing them to focus on the more strategic and creative aspects of their work. For me, the future is likely one where humans and AI collaborate to achieve even greater outcomes.
Zuckerberg’s Controversial 2025 Prediction
Mark Zuckerberg's recent statement about AI replacing mid-level engineers by the end of 2025 is certainly headline grabbing and sparks important discussion. It's a bold claim and while I acknowledge the rapid advancements in AI, particularly in coding and software development, I believe the reality is much more nuanced.
AI is undoubtedly becoming an increasingly powerful tool. We're already seeing AI automate certain development tasks, boosting developer efficiency. However, software engineering is a multifaceted discipline. Beyond coding, it involves understanding user needs, complex problem-solving, system design, and crucially, collaboration. While AI can excel at specific coding tasks, these broader responsibilities require human judgment, creativity and strong communication skills—areas where humans still have the advantage in 2025.
Mid-level engineers play a vital role in our teams. They tackle complex projects, often lead smaller teams, and mentor junior engineers. AI can undoubtedly assist with these tasks, but I foresee it being a valuable support tool rather than a complete replacement in the near future. I believe we'll see AI empowering our engineers even more, making them more productive and efficient, and allowing them to focus on the more strategic and creative aspects of their work. For me, the future is likely one where humans and AI collaborate to achieve even greater outcomes.
Core or Context
One of the challenges of heading up an engineering team is strategically allocating your resources to maintain your competitive edge. A key aspect of this is distinguishing between 'Core' and 'Context' activities.
In ‘Dealing with Darwin’, Geoffrey Moore introduced the Core and Context model as a way of focusing scarce resources on maintaining a competitive advantage; companies can categorise their processes into two main groups.
'Core' activities are the unique technical capabilities and knowledge that differentiate us in the market and deliver maximum value to our customers. These are the essential processes and activities that directly contribute to creating and delivering our unique products or services.
'Context' activities, while still important, are the supporting infrastructure and general business functions that enable our core activities. These elements are necessary for smooth business operation but don't directly contribute to creating our unique value proposition.
This concept is applicable to all business areas, but I find it especially useful in keeping software development teams focused. I've frequently been asked to develop products that are already available on the market. The rationale given is that purchasing a third-party product is costly and we can create it internally for much less. While this may be true at the outset, the end result is often an inferior product compared to the third-party offering with negligible cost saving, as they have the resources and focus to specialise in that specific product.
The Core/Context model helps businesses prioritise what truly matters to their customers. For example, customers are more likely to value a new feature or product that directly benefits them, rather than be impressed by an internal CRM system similar but inferior to products readily available on the market.
However, simply categorising work into these two areas isn't enough. A more strategic approach involves considering available external solutions, specific business needs and the cost-benefit analysis of different options.
The decision of whether to build capabilities in-house or leverage external expertise is crucial. It requires careful evaluation of your core strengths, available resources and the potential risks and benefits of each option. By focusing on core activities and strategically using external expertise for context activities, we can optimise our resource allocation and achieve greater overall efficiency.
#SoftwareDevelopment
#CTO
#Brainlabs
#geoffreyamoore
Core or Context
One of the challenges of heading up an engineering team is strategically allocating your resources to maintain your competitive edge. A key aspect of this is distinguishing between 'Core' and 'Context' activities.
In ‘Dealing with Darwin’, Geoffrey Moore introduced the Core and Context model as a way of focusing scarce resources on maintaining a competitive advantage; companies can categorise their processes into two main groups.
'Core' activities are the unique technical capabilities and knowledge that differentiate us in the market and deliver maximum value to our customers. These are the essential processes and activities that directly contribute to creating and delivering our unique products or services.
'Context' activities, while still important, are the supporting infrastructure and general business functions that enable our core activities. These elements are necessary for smooth business operation but don't directly contribute to creating our unique value proposition.
This concept is applicable to all business areas, but I find it especially useful in keeping software development teams focused. I've frequently been asked to develop products that are already available on the market. The rationale given is that purchasing a third-party product is costly and we can create it internally for much less. While this may be true at the outset, the end result is often an inferior product compared to the third-party offering with negligible cost saving, as they have the resources and focus to specialise in that specific product.
The Core/Context model helps businesses prioritise what truly matters to their customers. For example, customers are more likely to value a new feature or product that directly benefits them, rather than be impressed by an internal CRM system similar but inferior to products readily available on the market.
However, simply categorising work into these two areas isn't enough. A more strategic approach involves considering available external solutions, specific business needs and the cost-benefit analysis of different options.
The decision of whether to build capabilities in-house or leverage external expertise is crucial. It requires careful evaluation of your core strengths, available resources and the potential risks and benefits of each option. By focusing on core activities and strategically using external expertise for context activities, we can optimise our resource allocation and achieve greater overall efficiency.
#SoftwareDevelopment
#CTO
#Brainlabs
#geoffreyamoore
Unwrapping the Solution
Throughout my years in software engineering I've seen a consistent pattern: Users, whether internal or external, often approach developers with solutions they want built. "We need a button that does X," or "Can we create a report that shows Y?" are common requests.
While these suggestions are valuable, the first and most crucial step for product engineers and product managers is to peel back the layers and understand the underlying problem.
Why do they want that button? What specific insights are they trying to gain from that report?
By focusing on the "why," we shift from simply implementing a requested feature to truly solving a need. This approach offers several key benefits:
Clarity: It ensures everyone is aligned on the actual problem being addressed.
Innovation: It opens up possibilities for more effective and creative solutions. Sometimes, the initial "solution" is just one of many ways to tackle the problem.
Efficiency: It prevents wasted effort on building features that don't truly address the core need.
User Collaboration: It enforces a collaboration between engineers, product managers and users, to make sure the best solution is found.
At Brainlabs, we encourage our teams to ask "why" relentlessly. This practice, combined with our deep understanding of digital marketing, allows us to build cutting-edge technology that truly empowers our agency.
#SoftwareEngineering
#ProblemSolving
#Innovation
#Brainlabs
#TechLeadership
Unwrapping the Solution
Throughout my years in software engineering I've seen a consistent pattern: Users, whether internal or external, often approach developers with solutions they want built. "We need a button that does X," or "Can we create a report that shows Y?" are common requests.
While these suggestions are valuable, the first and most crucial step for product engineers and product managers is to peel back the layers and understand the underlying problem.
Why do they want that button? What specific insights are they trying to gain from that report?
By focusing on the "why," we shift from simply implementing a requested feature to truly solving a need. This approach offers several key benefits:
Clarity: It ensures everyone is aligned on the actual problem being addressed.
Innovation: It opens up possibilities for more effective and creative solutions. Sometimes, the initial "solution" is just one of many ways to tackle the problem.
Efficiency: It prevents wasted effort on building features that don't truly address the core need.
User Collaboration: It enforces a collaboration between engineers, product managers and users, to make sure the best solution is found.
At Brainlabs, we encourage our teams to ask "why" relentlessly. This practice, combined with our deep understanding of digital marketing, allows us to build cutting-edge technology that truly empowers our agency.
#SoftwareEngineering
#ProblemSolving
#Innovation
#Brainlabs
#TechLeadership
When I hire software developers, I always look for people who are passionate about technology and here is why:
They are more likely to be engaged and motivated. When devs are passionate about tech, they are more likely to be engaged in their work and motivated to produce high-quality results. They are also more likely to be excited about learning new technologies and staying relevant.
They are more likely to be creative and innovative. Passionate developers are more likely to think outside the box and come up with creative solutions to problems. They are also more likely to be willing to experiment with new technologies and approaches.
They are more likely to be team players. Passionate developers are often eager to share their knowledge and expertise with others. They are also more likely to be willing to help out their teammates and collaborate on projects.
They are more likely to be successful. Developers who are passionate about tech are more likely to be successful in their careers. They are more likely to be promoted and to earn higher salaries. They are also more likely to be satisfied with their jobs and to stay in software development for the long term.
For these reasons, I feel it's important to hire software developers who are passionate about technology. By doing so, you can create a team of developers who are engaged, motivated, creative, innovative and successful.
#Brainlabs
#SoftwareEngineering
When I hire software developers, I always look for people who are passionate about technology and here is why:
They are more likely to be engaged and motivated. When devs are passionate about tech, they are more likely to be engaged in their work and motivated to produce high-quality results. They are also more likely to be excited about learning new technologies and staying relevant.
They are more likely to be creative and innovative. Passionate developers are more likely to think outside the box and come up with creative solutions to problems. They are also more likely to be willing to experiment with new technologies and approaches.
They are more likely to be team players. Passionate developers are often eager to share their knowledge and expertise with others. They are also more likely to be willing to help out their teammates and collaborate on projects.
They are more likely to be successful. Developers who are passionate about tech are more likely to be successful in their careers. They are more likely to be promoted and to earn higher salaries. They are also more likely to be satisfied with their jobs and to stay in software development for the long term.
For these reasons, I feel it's important to hire software developers who are passionate about technology. By doing so, you can create a team of developers who are engaged, motivated, creative, innovative and successful.
#Brainlabs
#SoftwareEngineering
The last couple of days spent in Charlotte, North Carolina, connecting with fellow CTOs from the Falfurrias Management Partners portfolio were fantastic. Huge thanks to Joe Oesterling for organising the inaugural CTO Summit – it was an invaluable chance to learn, share insights, and make real connections. The agenda was full of thought-provoking sessions, leading to great discussions about key areas for our technology strategies.
While virtual meetings are useful, the energy and deeper connections from meeting in person were clear. This summit has set up a strong base for ongoing collaboration and sharing knowledge with this talented group of tech leaders. I'm excited for future interactions and using these new connections as we keep building cutting-edge technology for our companies.
#CTOSummit
#TechnologyLeadership
#Innovation
#Collaboration
#SaaS
#GenAI
#DataAnalytics
#Brainlabs
The last couple of days spent in Charlotte, North Carolina, connecting with fellow CTOs from the Falfurrias Management Partners portfolio were fantastic. Huge thanks to Joe Oesterling for organising the inaugural CTO Summit – it was an invaluable chance to learn, share insights, and make real connections. The agenda was full of thought-provoking sessions, leading to great discussions about key areas for our technology strategies.
While virtual meetings are useful, the energy and deeper connections from meeting in person were clear. This summit has set up a strong base for ongoing collaboration and sharing knowledge with this talented group of tech leaders. I'm excited for future interactions and using these new connections as we keep building cutting-edge technology for our companies.
#CTOSummit
#TechnologyLeadership
#Innovation
#Collaboration
#SaaS
#GenAI
#DataAnalytics
#Brainlabs
Nine years ago, I joined Brainlabs at a point where I was pretty burned out and looking for a different kind of work culture. What I found here was exactly that – a refreshing and supportive environment.
Seeing the Brainlabs Handbook early on was the decisive factor for me. It highlighted a real commitment to its people, something I hadn't experienced in my previous role. Over the years, this has translated into a genuine opportunity for growth and learning.
One thing that stands out is the power in saying, "I don't know." It might sound simple, but it's fostered a culture of trust, innovation and improved decision making. When a response is given, it is considered and composed, not rushed or from a place of insecurity or pressure.
Grateful for the past nine years of growth and support at Brainlabs. It's been a journey of continuous learning in a place that values honesty and teamwork.
Here's to what's next!
#Brainlabs
#WorkCulture
#ProfessionalGrowth
#TeamCollaboration
#HonestyInBusiness
#Anniversary
Nine years ago, I joined Brainlabs at a point where I was pretty burned out and looking for a different kind of work culture. What I found here was exactly that – a refreshing and supportive environment.
Seeing the Brainlabs Handbook early on was the decisive factor for me. It highlighted a real commitment to its people, something I hadn't experienced in my previous role. Over the years, this has translated into a genuine opportunity for growth and learning.
One thing that stands out is the power in saying, "I don't know." It might sound simple, but it's fostered a culture of trust, innovation and improved decision making. When a response is given, it is considered and composed, not rushed or from a place of insecurity or pressure.
Grateful for the past nine years of growth and support at Brainlabs. It's been a journey of continuous learning in a place that values honesty and teamwork.
Here's to what's next!
#Brainlabs
#WorkCulture
#ProfessionalGrowth
#TeamCollaboration
#HonestyInBusiness
#Anniversary
