Business and IT speak a different language. This is a challenge for many organizations as it hinders communication about requirements in IT projects. An often suggested way to deal with this problem is to use the simple and fixed format of user stories to express requirements (as a..., I can... so that ...) and I fully agree on this. However, as a business analyst, I notice a lot of confusion among business people when it comes to the definition of a user story. I often hear that user stories are too technical for them. In this blog post I provide 4 tips to write user stories that express business requirements making sense from a business point of view.
We are creating customer journeys on the fly these days. It is the revelation in process modeling and customer understanding. By combining the outside-in process of the customer with his emotions we are able to steer our organization towards the customer-centric culture, and foster loyal customers. But in our quest for the outside-in enterprise, one must not forget why we are mapping a journey in particular. Forrester states there are 6 possible goals for every customer journey map.
Building a profitable enterprise no longer depends on finding the right product and setting the right price. We live in the age of the customer, who is well informed through the capabilities of the internet. Customer Experience has become an important element in doing good business. Companies will have to reinvent themselves in order to fully understand and serve their customers, employees and partners. Time to get started on building amazing experiences, aided by digital tools. We spoke with Kenny Follet, one of the speakers at AE's latest AE Foyer "Embrace your customer, get digital!"
Do you recognize the following situation? You are involved in a project and, based on a slide deck or analysis document, you need to decide on the way to go. After reading the content, you don’t feel like you’ve fully grasped it and you don’t feel comfortable at all to take a decision. In this article, I’d like to share 3 practical tips to increase the value of any change/requirements document, enabling faster and more confident decision taking for stakeholders.
So we have analysed the customer's journey, looking not only at the different steps our customer goes through, but also how he feels along the way. We've also checked the different touch points the customer interacts with and identified gaps or points for improvement. Useful techniques that help us better serve the customer. But one question is left untouched: does the customer care?