How To Make Your Clip On Hair Extensions Thicker
The bigger the better. I started this post to share all the best resources and ideas I found online but soon realized I had so much info I wanted to share that my one post was really a series of posts. So this is the first post in this Big Sexy Sixties Hair series.
In this post we will look at how to DIY your own thick clip on hair extensions. Whether you have thinning hair like me (more on that below), are born with thin fine hair, or just want to have some fun with your hair, clip on hair extensions can be a great solution. Who doesn't want to have thicker longer and fuller hair some days, It was my first time buying any hair extensions and I went with what the sales person suggested (I bought mine at Hair Plus Beauty Supply in Minneapolis).
By always working with a set order of priorities, adjustments and changes are easy to make. If, by some miracle, more time or resources are found in the schedule, it’s clear what the next most important item is to work on. By the same token, if the schedule needs to be cut, everyone knows what the next least important item is and can stop working on it. This is incredibly important because it guarantees that no matter what happens, you will have done the most important work possible and can make quick adjustments without much effort or negative morale.
Also, any prioritization mistakes you make will be relative: if work item 10 turns out to have been more important than work item 9, big deal. Because the whole list was in order, you won’t have made a horrible mistake. And besides, by having such clear priorities and keeping the team focused on them, you may very well have bought the time needed to get work item 10 done after all.
Figure 13-1. The three most important ordered lists, shown in order. Other important things that might need ordered lists include bugs, customer suggestions, employee bonuses, and team budgets. They can all be managed in a similar way: put things in the order most likely to make the project or organization successful. No matter how complex the tools you use are (say, for bug tracking), never forget that all you’re doing is ordering things.
If the tools or processes you use don’t help you put things in order and carry out that order, find a different tool or process. Bug triage, for example, where people get in a room and decide when a bug should be fixed (if at all), is really just a group process for making an ordered list of bugs.
The bugs might be classified by group rather than on an individual bug-by-bug basis, but the purpose and effect are the same. If you do use the three most common ordered lists, make sure that they always map to each other. Every engineering work item should map to a feature, and every feature should map to a goal. If a new work item is added, it must be matched against features and goals.
This is a forcing function to prevent random features. If a VP or programmer wants to slip something extra in, she should be forced to justify it against what the project is trying to achieve: “That’s a great feature, boss, but which goal will it help us satisfy, Typically, these ordered lists have one important line dividing them into two pieces.
The top part is priority 1: things we must do and cannot possibly succeed without. The second part is everything else. This priority 1 line must be taken very seriously. You should fight hard to make that list as small and tight as possible (this applies to any goal lists in the vision document as well). Putting this line in place was always very difficult; there was lots of arguing and debating about which things customers could live without or which things were more important than others.
