In technology, we often lose sight of the human equation. That seems counterintuitive for customer-based platforms, doesn’t it?

by Jul 3, 2023

In technology, we often lose sight of the human equation. That seems counterintuitive for customer-based platforms, doesn’t it?

We talk so much about integration and automation in Dynamics 365, or any other system for that matter, but we spend comparatively little time discussing the people who will actually use these systems.

When working on a new project or implementing a new solution, how often do we stop and ask ourselves Who is this really for? What will this change mean in their everyday lives?

In my experience as a Power Platform architect, I’ve found that the best solutions are always designed with end-users in mind. They aim to simplify tasks, improve workflow and ultimately contribute to a seamless user experience.

As professionals in technology, let’s strive to ensure our solutions are not just smart but also empathetic!

Have you ever been part of an integration process where ’empathy’ played a key role in its success?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more