We are
punctilious
when it
comes
to quality

Our team

View our application experts/integration specialists/football loves/sit-down comedians/food connoisseurs/film fans/globetrotters/Zen specialists… and read how they personally make the complex simple.

  • Axel Trip

    “To make the complex simple, I start with a simplified version of the complex reality. As soon as this simplified version is understood by everyone, I add the complexity in steps of applicable size to keep it understandable for all parties.”

  • Bas van der Horst

    “In complex cases, my first step is always to understand the true goal. What do you want to achieve and why? When you know that, it becomes easier to set priorities and come up with the right solution.”

  • Dennis Homberg

    “If I want to be able to explain a complex problem, I use reverse engineering. By asking the right questions and walking all possible routes of an end-user in the opposite direction, I can often immediately identify a cause.”

  • Edwin Bergamin

    “Advising on issues at the intersection of Business & IT is often complex. By keeping the customer’s goal in mind and using the right expertise, I keep it simple. In this way, Mendix’s ‘Go make IT’ contributes quickly and easily to the digital ambitions of our partners.”

  • Gabe Vader

    “The challenge is to find the simplest possible solution to a complex problem. In programming, you always do that by discussing it first, making overviews and, if possible, sleeping on it overnight and dividing the problem it into pieces (sub-micro-flows).”

  • Hans Roks

    “If I want to make something complex simple, I draw it out. Making an overview in the style of a prompting board, you immediately make every conversation a lot more practical. Also, I like to stand in front of a whiteboard, visualising thoughts so that they become understandable.”

  • Jarno Koopman

    “When solving a complex software problem, I always look for all ways to find the source of the problem. By focusing on this, I limit the area I have to focus on, making it easier for myself to solve the problem.”

  • Jason Teunissen

    “Can we increase usability by reducing noise?”

  • Joel van de Graaf

    “IT landscapes are becoming larger and more complex due to the growth in the number of systems. By relating business processes to application services and functions, I create an overview of structure, coherence and reuse for now and for the future.”

  • Joey Baten

    “Complexity arises because application landscapes are increasing in size due to continuous development. By decreasing the size of distributions, e.g. functionalities and business processes, I ensure that complexity is easier to understand.”

  • John Cornegge

    “A lot of issues are part of a higher-level process where the business expects a certain result. It helps me to outline this process so that it becomes clear how each individual part influences the chain.”

  • Joost Ahrens

    “As a system consists of more components, the chance that something goes wrong increases. I avoid complexity by eliminating dependencies and unnecessary actions. Ultimately, the simple remains.”

  • Karim Harmak

    “Building complex processes is very simple within the integration landscape. The challenge lies more in building simple processes where ultimately a complex issue is solved.”

  • Martin de Heer

    “If I come across something complex, I cannot source myself to fathom it at once. Instead, I put it aside for a while to pick it up later. While I am not working on it actively, I unconsciously create new insights.”

  • Michella Fijneman

    “In my position, I have to deal with various tasks. I keep the overview by dividing the whole, as a large pizza, divided into slices with a different topping on each slice. The individual slices are easy to understand, but as a whole, they form a varied pizza!”

  • Minke van Dooremalen

    “Marketing in itself is extensive and has many types of specialisation. What helps me is to split all tasks into small pieces. Then, when you put everything back together like a puzzle, you have an overview of the comprehensive strategic field and you can contribute to the business objectives!”

  • Patrick Verhoeven

    “Metaphors are extremely effective for shedding light on a specific problem. They enable us to temporarily distance ourselves from our usual way of thinking and see the larger picture. This way, I always make sure that business and IT understand each other.”

  • Paul Schreur

    “I apply what I learned as an organic chemist in my daily life as a developer. After analysing the complexity of a problem, the synthesis of the fragments will lead to a simple solution.”

  • Pim van der Noll

    “Domains of applications, system landscapes and processes are sometimes difficult to understand. By speaking to the experts from those domains, I understand how things are connected. The individual parts are then standalone and simple.”

  • Remco Tuerlings

    “For me, simplifying complex customer requirements always starts with the preparation of clear User Journeys. By working out these journeys, we establish what the core goals and side issues are, allowing us to tackle the elements that cause the noise.”

  • Ronald Beer

    “Complexity often arises due to a lack of knowledge; if you look deeper, it often turns out to be less complex. If I run into something that I experience as complex, I ask a whole array of questions, trying to take on a different perspective, increasing my knowledge.”

  • Sjaak Overgaauw

    “Many IT landscape systems are unnecessarily complex due to the use of outdated technologies. Every day, I am involved in designing solutions that make the business side of the company happy and where IT can have an impact. It provides you with flexibility, a better functioning company and growth opportunities for the company.”

  • Sven Ernest

    “Complex challenges require simple processes! I make complexity simple by first identifying the desired goal, thereby defining the scope. By making the goal clear for myself, the journey to get there becomes clearer and simpler.”