As we continue to move forward discussion object-oriented programming in WordPress, it’s important that we make sure we’re not jumping ahead of ourselves when it comes to building a product for someone else.

So often, it’s easy to:

1. hear what a customer says,
2. build something out based on what we’ve heard,
3. turn it over to said customer.

But there is so much more to it than that. I’ve danced around it a bit in previous posts in this series; however, I want to start drilling down into what it means to hear:

1. What a customer says,
2. Develop a set of requirements,
3. And then create feedback loops around that.

Ultimately, we want to make sure the people for whom we’re working the and solutions that we’re building truly are solutions and not hindrances or hurdles over which they have to jump.

Furthermore, I don’t think it’s enough that a customer simply enjoys the experience of their final product, but with working with the one (or the ones) building the solution, as well.

With that said, let’s take a look at what it means to listen what they say and go from there.

Continue reading