How to become a good analyst in IT?

Question

Project management

Hello. I've only been working as an IT analyst for a couple of years, actually combining the functions of a business and systems analyst. Recently I came to work in a startup, where I am now the only analyst, in fact I am the analytics lead. Unlike the companies where I worked before, here I am responsible for all analytics in the company, in terms of business and system parts. And I ran into the problem that I can't build a process around my work. I am required to write technical documentation, and formalize business requirements, but I seem to have a stupor, no matter what I undertake - I face a wall of uncertainty. My previous experience from more or less large companies does not work here.

Hence a few questions:
1) Perhaps someone has already encountered this before and can tell about their experience?
2) I don’t have a lot of work experience and I am aware that I may lack some competencies to build the correct approach, if someone has articles or materials that you could advise me - with pleasure accept!
3) Perhaps there are some specific methods or tools for resolving situations like mine, when nothing is clear anywhere, but you need to achieve certainty and get results in a short time, if you recommend courses or materials, I will also be very grateful!

Thank you all in advance!

Answer 1

If you are an analyst then use these skills to achieve your goal. Form a goal, identify weaknesses, lack of competencies, decompose. If you cannot do this, then you are not an analyst, but an impostor. Analyst is one of the most flexible professions where skill number zero is coping with new problems.

Answer 2

See my question for an explanation. He really gave a good response. As for your situation, break everything down into subtasks and tightly control, then release the carts where you see the normal execution on schedule. Where is the fakap there, ask what is the plug, often people lock themselves up and dig in the wrong place, a simple question takes them to the right road, but you need to strike a balance between obsession and a gentle correction of direction

Answer 3

google hypothesis testing

Answer 4

My previous experience from more or less large companies does not work here.
Are the requirements for creating working technical documentation different at the new workplace? In what? In the applied software? The same pain with the formalization of business requirements? And the result should be yesterday? Then, yes, - one utopia (

Answer 5

3) Perhaps there are some specific methods or tools for resolving situations like mine, when nothing is clear anywhere, but you need to achieve certainty and get results in a short time, if you recommend courses or materials, I will also be very grateful!

There is a methodology - Domain Driven Design, but it's not about just once and for money at the cash desk, it's about the project as a whole, how to reduce its complexity. And DDD is not limited to business or systems analysis, it is about all participants, including customers and developers.
A more particular solution is to study the subject area well, to study the software architecture well.