Good Enough

Question of the week: I don't have enough content to fill the document of Identifying Existing Systems

I write this article based on the insight of my conversation with my team in our monthly 1-on-1 call. I speak with each one of my team members. This article is to share the question of this week and our method to work on it. You can subscribe to the Building Our Team newsletter (2100+ subscribers)

Photo by AI (Midjourney)

I don't have enough content to fill the document of Identifying Existing Systems

Firstly start putting all the information that you already have in the format that is mentioned in the goal sheet from row 55 cell A.?

In A 55 there is a document template where you can start filling up the three paras and all the other information.

If you think you have less information, you can do one of the following three things.?

1. Revisit the document in a day or two, attack each question separately, and see if you can fill in any more information or any variation of information that you can add somehow; your subconscious mind will help you. You will add a line or two more.

2. Go to your peer’s documentation. Currently, there are a couple of them who have added the points to the document, which is why it is important that even if your work is not completed, your documentation is half, even if you have the title of identification is important for you to paste it and put it the link in there so that others can get a little bit of inspiration. You check with other people's work and see what related points or topics you can mention about your own document that you might have missed.

3. Set up the comment on your document. Finish up your first draft, do steps 1 and 2; and you still think that your document is not up to the mark or it lacks information, then send it across to some of your Leads or the Leader group in your peer and ask them to put some comments to add more details or you can send it to me, and I will be able to help to bridge the gap. I'm sure I will ask you a couple of questions or highlight the missing points, and you can either accept it or reply with your answer. Why is that not a good option??

Here are some simple hacks to fill in the data. You can mention some bad examples you can say about actual time spent, some examples from the past or actual time saved, you can mention constraints like the total number of people need to put in the total time block this particular system should take, what time do you recommend to do this activity during your day, when you should not do the activity, what are the bad examples links of any tickets with the bad examples, what are some good examples, what are the thing that is common mistakes that done by some juniors here, what are some information that you think everyone knows. For example, userentry ID or Instance ID, but any link or reference documentation where it is amended. It could be some basic information that you can add up to fill it up.

If you liked this, why not share it?