A stakeholder is anyone affected by a change, anyone who has a say in it, and anyone who can make it fail. That is wider than the people in the kickoff meeting. Start your list from the change itself: for each step that changes, ask who does it today, who uses its result, who pays for it, who supports it and who checks it.
The groups people forget are the ones who never asked for the change: the support desk that gets the calls when it breaks, the team downstream that receives its output, auditors and regulators, and customers who will notice a new step. Missing one of them is how a project learns about a requirement two weeks before go-live.
Keep the list as a short register: the stakeholder, their role in the change, what they need and how much they can influence it. The next lessons sort it.