Measure Sloppy
Vikram Shetty ??
The ROI Guy ? I help DEI Consultants get more warm leads ? Download my ROI of DEI white paper to learn the framework (see featured section)
Questions of the week: How can we identify sloppy/patch/duct tape work? I don't have a complete idea about the system. How to implement it? What is the difference between process and system?
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 a compilation of a whole week's takeaway. You can subscribe to the?Building our Team?newsletter (1800+ subscribers)
How can we identify sloppy/patch/duct tape work?
There is no one standard way to find sloppy patchy or duct tape work.?
But there are some methods to identify them.?
1) Observe your work from an outsider's point of view, such as your lead or the best person from the industry who would see that work and critique it. It could help you see if the quality and standard of work stand out or is sloppy.
2) If you have to explain to someone repeatedly what you have done and it's not easily understood, even by your teammates or your team lead, then it is sloppy work.
3) When you revisit the work after a couple of days or weeks, if you don't understand what's going on, how you did the work, or what changes you made, it is bad work.
4) Is there any change asked to be done? You kind of get irritated or frustrated because, you know, you have to start from the beginning and a lot of rework and possibility of breaking the work done so far
5) If Someone asks you to identify an error, bug or mistake, and you are not able to figure out how to fix it, it means you have done a patchwork.
6) There could be related work items like documentation, instructions, the naming of certain things or some additional information. Be it release notes, ticket updates for your teammates or clients, or some additional opportunities that could lead to new business or features. This means the work is not fully completed.
Above six points you can begin with that will help you find if you are doing patchy work or sloppy.
I don't have a complete idea about the system. How to implement it?
We have nine lessons as the first assignment of this year, with sets of basic questions that need to be answered to get more ideas on systems.
领英推荐
The best practice for studying this material are as follow:-
1) Watch the videos and read the articles provided.
2) Read the accompanying book and take note of any unfamiliar terms and concepts related to Systems, Subsystems, Procedures, Processes, Checklists, SOPs, System mindset, Strategy and also different definitions and literature around it.
3) To have a five-minute call, just five minutes on one topic, one particular word or a definition that you don't understand with any of your team members who has a fair bit of an idea on that topic or at least their point of view.
At this point, do not worry about how you will implement it. It is as good as if you don't know how to make tea; you cannot.?
So, the first job is to understand what the system is. Once you understand, its implementation will come naturally and more easily.?
So, when you get to this question, Check if you have done your homework and all the assignments. Even if you do it, you can understand the system's concept.?
At least start with a bad system, a wrong system, or an imperfect system. By doing this, you will have an understanding & by comparing notes with your team members. Your knowledge of the system will improve.
What is the difference between process and system?
Processes are the parts of subsystems. So systems are composed of subsystems which can again consist of a subsystem.?
There is no direct measurement as such, but each subsystem will have a set of processes that needs to be followed and thus really help effectively conduct the system.?
So processes will be the moving parts that comprise a subsystem, and it helps things to happen in a sequence.?
For example,
All the steps we have are part of a process. The step in the process will not directly guarantee the result of the team’s cultural goal. However, it will guarantee the gaps in the knowledge of the system. It will also bridge the gap between someone building the system and eventually improving the system.
The team’s effort in investing one hour per day will be more effective and efficient in delivering high-quality results to our clients and making a profitable return to 73bit.