About systematization of information resources
Hi all!
When looking for a job, I was often asked: who do I see myself as – a performer or a leader? I never understood this question, but the answer is obvious:
And then one day I was lucky to meet my “petty tyrant”:
A petty tyrant is a tormentor,” don Juan explained. – Someone either has the power over the life and death of a warrior, or simply irritates him to the point of madness (Carlos Castaneda).
So I understood the difference between boss and leader. This led to an unexpected conclusion – I am not happy with the question asked above. What's the point of being a performer all your life? Or a supervisor, without getting out of constant “calls” and planning tasks?
This article is a collection of thoughts on a subject that is interesting to me. Just share.
One day I wanted to master 1C and not pay for training. I came to their office, where they recommended that I take 2 books – a textbook and another one with the base. When I installed everything and started reading, I realized that nothing was clear: “you can do this, you can do that…” And where are the guides that I need? need to What should I do to understand how it works? Okay, apparently I came across such a textbook.
Next, I often encountered the need to defragment information so as not to keep all the nuances in my head. Here, usually everyone bothers themselves, for example, as in the article: How to organize a personal knowledge base for a developer, but I decided to go further. What if we shifted our focus from the private to the corporate? Judging by the description in Wikipedia this applies to management consulting of an organizational type. So I began to systematize the company’s information resources.
Information resources should be understood as everything that allows you to evaluate the company’s product and its production processes: website, knowledge base, comments in tasks, training materials, interviews, employee work regulations, etc.
Tasks
Increasing the attractiveness of the product and the level of maturity of the company:
Development of a knowledge system about a product or service.
Description of production processes for their optimization.
Development of regulations and instructions.
Benefits
For the company:
The attractiveness of the product expands the customer base;
Quality service creates long-term relationships;
Improving employee performance;
Implementation of SLA improves business reputation.
For company employees:
Good mood 🙂
Increasing motivation for development;
Reducing the risk of demotivation in complex subject areas.
For clients:
Improving the quality of our own services;
Reducing risks in long-term relationships;
Reduced technical support costs;
Maintaining a positive business reputation.
About systematization
Systematization includes several types of activities:
Project management. Because putting things in order is always uncertainty and finitude. For those who believe that “repairs cannot be completed, they can only be stopped” – implementation also always ends with transfer to operation. There is no point in supporting walls on a crooked foundation indefinitely.
Business Analytics. Typically, companies display some kind of indicators on their website. They must be well-calculated and indicative.
Example:
Why carry out any systematization if the company has no purpose? It will just be a waste of time.
Process analytics includes all 3 phases: white (description of “as is”), gray (development of “to be”) and black (implementation of a new process).
Technical description – building a knowledge system about the company’s product or services.
Copywriting – useful skill for creating/maintaining landing pagebecause It is unlikely that a manager making a decision to purchase a company’s product or services will read any instructions on software settings.
Methodology – this is about creating instructions and regulations. It is not enough to know all the aircraft systems to fly. We also need the correct sequence of actions.
