Michael Annis’ Post

View profile for Michael Annis, graphic

Fractional Chief Automation Officer (fCAO) | Digital Transformation Consultant | CPA | Geneva Investor Accounting SME | Private Equity/Hedge Fund Automation |

Had this recently: Client: "We want to use X data to do Y." Me: "Here you go." Two weeks later: Client: "Well, we actually want to be able to modify parts G and F." Me: "So, what if I build all the possible modification options in this medium, so you can use X to do Y while modifying G and F and several options that may come up in the future?" Client: "Yeah, that's great!" Six weeks later: Me: "Here you go, as requested." Client: "Well, we actually want the original medium (that doesn't support the calculation), not the medium you used, and it's no longer just use X to do Y, it's use X to do Y with a completely different calculation than we originally told you. Oh, and add the ability to add on R as needed." Me: 👀

Customers: Do you struggle to clearly communicate your needs to vendors? Vendors: Do you find yourself on the sixth iteration of a project that seemed simple at the start? Effective communication is a two-way street. Whether you're a client seeking the right vendor or a vendor delivering on a project, clear communication is essential. Clients need to articulate their needs and expectations, while vendors must actively listen and respond accordingly. A straightforward approach can help both parties align better: Mandatory Requirements: What must the solution accomplish? If it doesn’t meet these criteria, it’s a dealbreaker. Preferred Requirements: What would be nice to have? These are features you’d appreciate but can live without, or find a workaround for. Optional/Not Needed: Everything else. For clients, write down these requirements and review them regularly. For vendors, check off these requirements as you meet them. If, after meeting the original objectives, additional features are requested, it’s important to acknowledge that scope creep may occur—and this often requires additional budget or time. Consider this perspective: Would you rather hear from a client, "Well, we thought it was going to do X," or "Thank you for meeting all the requirements. After further consideration, we’d like to explore making feature Y a mandatory objective. Can this be accommodated within our current budget?" Remember, 95% of people are doing their best to satisfy their clients while maintaining fair compensation. Overcommunication is always better than undercommunication. Hyper-organization is better than chaos. It’s easier to dial back from overcommunication and hyper-organization than to piece things together when issues arise without clear records. Start strong and find the right balance as you go.

  • No alternative text description for this image

To view or add a comment, sign in

Explore topics