Upgrade & Secure Your Future with DevOps, SRE, DevSecOps, MLOps!
We spend hours scrolling social media and waste money on things we forget, but won’t spend 30 minutes a day earning certifications that can change our lives.
Master in DevOps, SRE, DevSecOps & MLOps by DevOps School!
Learn from Guru Rajesh Kumar and double your salary in just one year.
Anyone new to AIOps soon learns that a recommendation never arrives alone. Somebody in a design review says “we should use this correlation engine,” and the room nods, and only later does it come out that the speaker used to work for the company that makes it. Nothing about that history is shameful. What hurts is that nobody heard it when the nodding happened. This primer is about one habit that fixes the problem: saying what is in it for you, in a plain sentence, every time you recommend an AIOps tool or approach.
Why a tie matters more in AIOps than in most fields
AIOps products sit in the middle of your operations. They ingest events from monitoring, group them, suggest causes and sometimes trigger actions. Once one is wired in, replacing it is a project of its own. That means the person who proposes it is shaping the next several years of the team’s work, and the room deserves the full picture of where the proposal comes from.
A tie is any relationship that could tilt your view. Maybe you were employed by the vendor, maybe you hold shares, maybe the vendor paid for your conference ticket, or maybe your consulting firm resells the product. Each of these is ordinary. Together they form the context a reader needs to weigh your words.
A mini-glossary for newcomers
- Disclosure: one plain sentence, placed before the recommendation, naming the interest you hold.
- Tie: a past or present link to the vendor, such as a job, a contract, a gift, a shareholding or a referral arrangement.
- Design review: the meeting or document where a team decides how a system will be built and which components it will use.
- Event correlation: grouping many raw alerts that share a cause into one incident so humans read fewer messages.
- Proof of concept: a small trial in a safe corner of the estate, run before anything is rolled out widely.
- Lock-in: the cost of leaving a tool once your data, dashboards and habits are built around it.
A concrete review, step by step
Picture a platform engineer preparing a design document for a team that wants to cut the volume of pages reaching the on-call rota. Three candidates are on the table: a commercial correlation product, an open-source engine and a homegrown rules layer. The engineer has spent two years at the company behind the commercial product and left on good terms. Their preference is obvious from the first draft.
The weak version of the document says, “The commercial product has the strongest topology awareness, so we should adopt it.” The stronger version opens the recommendation section with: “Before you read on, I worked at this vendor until last year and still hold a small number of shares, so please read my preference with that in mind.” That single sentence changes how every later paragraph is read. Reviewers who would have wondered about motive now simply evaluate the claims on their merits, and they may even trust the strong points more because the author was upfront.
The engineer then does two further things that fit the habit. First, they ask a colleague with no tie to run the same test data through all three candidates. Second, they write down which claims come from firsthand use and which come from the vendor’s own material.
Where the sentence belongs
Placement is half the skill. A disclosure buried in a footnote does little. Put it where the reader’s attention is highest: the first line of the recommendation, the top of the slide, the opening of the pull request description, or the start of the chat message that proposes the tool. If you present out loud, say it before the demo, not after the questions begin.
Keep it short and factual. “I used to work there” is better than a paragraph of reassurance. Avoid adjectives that try to defuse the tie, such as “only a little” or “years ago, so it hardly counts.” Let the reader decide how much it counts.
What counts as a tie in practice
Beginners often underestimate how wide the net is. A free licence for a lab environment is a tie. A speaking slot at a vendor’s user conference is a tie. A friendship with the product manager is, at least, worth a mention. A referral fee from a link in your newsletter definitely is. The test is simple: if the other person learned this later from someone else, would they feel surprised? If yes, say it now.
A short note on how the habit spreads beyond tech
The idea is not unique to operations work. Creators and website owners who recommend things to an audience face the same question, and there is a website, CollabGigs, an online meeting point between advertisers that commission sponsored posts and the bloggers and video creators who carry them. Whichever way it is arranged, the underlying courtesy is the same one an engineer owes a review board: tell people what you stand to gain.
Common mistakes when starting out
- Waiting until someone asks. By then the disclosure sounds like a confession.
- Disclosing only to your manager, never to the wider group that will live with the decision.
- Treating a past employer as irrelevant once the notice period ends.
- Stating the tie but then arguing aggressively against alternatives you have never tried.
Wiring the habit into your team’s templates
The easiest way to make this stick is to give it a home in the paperwork. Add a short field to your design review template titled “My interest in this choice,” and make it a required line, even when the answer is “none that I know of.” Once everybody fills it in, nobody feels singled out for having a tie, because everyone has to say something. Over time it becomes as routine as listing the reviewers.
Teams just starting out may like the earlier walkthrough on introducing AIOps to a department calmly, and the write-up on calming event floods with sensible tooling gives a technical example of the kind of decision where a disclosure line would have helped.
Takeaways
Saying what is in it for you takes ten seconds and costs a little pride. In return the room can weigh your advice with open eyes, your future recommendations carry more credit, and the eventual tool choice rests on a record that nobody has to untangle later. Start with the next design document you write: one sentence, near the top, naming any job, share, gift or arrangement that touches the tool you are about to praise.