Those familiar with software development should know the Waterfall software development methodology very well. For those who don’t, it’s basically this: 1. Perform discovery/gather requirements 2. Build out the solution based on the requirements provided 3. Perform User Acceptance Testing (UAT) 4. Correct issues found during testing and resubmit for UAT 5. Repeat steps 3 and 4 as necessary 6. When the solution is accepted, prepare to move it into Production and do so 7. Support as necessary post-Production deployment
As a rule, we try to stay close to this approach when working through customer engagements, and regardless of the product we’re implementing it usually works very well. Continue reading →
This week I thought I would take the blog post in a different direction. Usually, we are focusing specifically on a technical topic and providing recommendations, solutions, theories and rants related to a topic. I would like to take a step back from the granular technical details and talk about relationships. Now I am not going to go and get all mushy, I want to focus on relationships in general that can be between any combination of entities and that will most likely apply to you. This topic applies to any type of relationship whether it is between management and employees, a company and their customers/partners, coworkers, friends and family. Enough prefacing, this week’s relations based topic is on the give and take aspect of our relationships.
Nobody likes to be involved in a relationship that is completely one sided. “I perform, deliver, provide, pay for, etc… with no reciprocation from the other side.” The purpose of this post is not to solve a specific problem or to get you to expect something in return for every little thing you do, but it is intended to get you to take a minute and evaluate the relationships in your life. It is common for us to take advantage of good relationships or relationships that we have the upper hand in, just as it is common for us to complain and/or lash out in relationships where we are being taken advantage of.
Let’s look at some examples of one sided relationships in business:
A customer spends money for a product or solution and the delivering company falls short in delivering the promised product, solution, or service. The customer will feel cheated and the company will lose out in future business.
A company continually delivers a quality product or successful solution to a customer, and an employee of the customer provides negative feedback regarding the company, solution, or service to attempt to reinforce their own value within their company. This can be tricky because the customer is paying for the product or solution, but this creates a hostile or negative relationship which will limit future success for the customer.
An employee continually performs at “above and beyond” levels and never receives appreciation from their company. The employee will feel taken advantage of and there will most likely be a negative impact to the company from losing productivity or losing the productive employee.
A company sells software for a vendor, and the vendor attempts to steal customers from the company. The company will feel cheated by the vendor and do less or no business with the vendor in the future.