Everyone wants to get more done. This often means putting aside quality for quantity. Sometimes you just don't have time to really do everything you want, so how do you ensure you're focusing on the stuff that really matters?
Ever wonder how some people seem to accomplish more with the same amount of time, or less? Is there some secret weapon to productivity that they use on a daily basis, if so what is it? That secret weapon is the Pareto Principle.
The Pareto Principle states that roughly 80% of your results come from 20% of your effort, known as the 80/20 rule. This means that most of your outcomes come from a small portion of things you are doing. So how can you apply this to becoming a better artist? And by "artist" I really mean "creator", whether it's traditional drawing, music, software development, 3D modeling, etc. The Pareto Principle can work for any field you're involved in, including creative fields.
If you post your digital art online, there are probably a few stand out posts while the rest are doing, well, OK. For example, on my Youtube channel, usually 3-5 videos do incredibly well while the 50 or so others are much less viewed. This tells me that I should replicate the high performers and not waste my effort on anything else.
If you knew which 80% of your effort was not working you wouldn't continue doing it, right? You'd focus on that 20% that is doing incredibly well and find out how you can continue doing that.
Pareto Maximizes What Matters
For your 3D models, perhaps the 20% that gets the most attention is all characters. With Pareto Principle in mind, you know that if engagement is your goal, you should focus on character work and ditch the rest.
With game development, building a massive game with a lot of unique game mechanics, you may realize that players REALLY love 3 mechanics used in the game and rarely use the others. In that case you may decide to really polish up those areas and make them shine even more.
This is something that game prototyping helps with, by figuring out what works and what doesn't. You can apply this approach to just about anything you do.
80/20 Rule for Learning
This being CGCookie, chances are you're looking to learn how to become a better 3D modeler, animator, or game developer. But there's only so much time in the day that you need to be selective about what you're learning.
Everyone wants the best "bang for your buck" and the internet is chocked full of information to learn from. CGCookie is no exception. But if you're watching every single course on our site or attending every live stream, you're not focusing enough. So how do you decide what to learn, Pareto style?
The Idea Tree
One thing I use quite often when I'm looking up courses or learning materials myself is how much value I'm getting beyond what is being directly taught. If what I'm learning has a super focused purpose, I'll probably pass up on it. Why? Because I want transferable skills and education that I can use in multiple scenarios.
If I'm learning how to animate a really custom rig that someone created, I may learn a thing or two about rigs, but if I can't seem to piece together how I would use this on my own then it isn't going to help me much.
The concept behind the idea tree is this: if I can picture myself using this knowledge for at least 2 different situations, it's useful enough to spend time learning it. By learning something that can be incredibly useful across a few different ideas that you have you're getting more "bang for your buck".
Using the 80/20 method, if learning one new thing allows me to do more by focusing on one project then it's a better use of my time. That one tutorial could be the 20% of tutorials that you watch, but ends up accounting for 80% of your new workflow through the techniques you've picked up from it.
An example of this is when I was learning how to create some unique shader effects. Let's take the dissolve effect which a lot of people have created. On it's own it's quite simplistic: you "dissolve" a part of the mesh from being rendered usually using a black and white noise texture. When I first saw this I had a few ideas on how I could use this:
- I could create a shield dissolving effect.
- I could use this to make a piece of paper "burn away".
- I could combine this with another texture to dissolve and reveal another texture below.
- Oooh I can also control the direction of this dissolve.
Done deal! This is worth learning because out of the one tutorial on the subject I can start to piece together an idea tree. Now with this one tutorial I can use this for a variety of purposes thus getting much more done rather than having to go through 4 or 5 tutorials or courses to learn.
If each of those tutorials is incredibly specific to one thing it can be much harder to get more use out of it, in which case you're focusing on the 80% that provides the 20% of value in return.
Find the educational resources that act as a Trojan horse of awesome ideas. Spend less time on a bunch of small "filler" pieces to learn from as your time is valuable. Stick with learning something that can truly provide value beyond the specific use case. Learn how to make the most of what you're learning. If a tutorial or course piques your interest start thinking about a few different ways you could use something.
Jump Start Your Idea Engine
At CG Cookie we teach the fundamentals to give you the tools needed to build what you want. It can take time and experience to really "connect the dots" to see past the tutorial project. But if you can, there's a wealth of techniques and knowledge to learn that can be applied to various projects. Tapping into the broader picture will jumpstart your idea engines.
How many ideas pop into your head when you see this Scifi Helmet course? If it's just a "scifi helmet" then you need to expand and think bigger. I see complex shapes that could be used to create a space craft or futuristic environments. I see unique eye sockets that could be used to create a mechanical camera of sorts.
Beyond that the kit bashing elements taught in the course make me think about this in a game development sense. Getting a base helmet in game, then using the same kit bashing technique to build a custom helmet players could create.
Think creatively about what you're learning, if you can't think this way about what you're deciding to learn then it may not be something worth spending time on. If you can't see yourself using what you've just learn on something you created yourself, then what is the point?
Learn Quicker with Relevance
When learning it's always a great idea to utilize something you already know well and use that as a basis of reference for whatever you're learning. This obviously doesn't apply to every circumstance, but relevance is the key to learning quickly. Being able to relate one idea to another will quickly get you up to speed.
There's a funny quote in the movie Road Trip that illustrates this:
Yeah, I can teach Japanese to a monkey in 46 hours. They key is just finding a way to relate to the material.
We all have something we can easily relate to and chances are we use this as a basis of learning other things. If you're learning a new programming language you'll more than likely reference a language you already know to quickly learn this new language. If you're coming from one 3d program like Maya, into Blender, you'll probably try to replicate the same workflow in Blender to get up to speed quicker.
One of the things I like to do most often is to find those things I can relate to and try to replicate that in whatever I'm learning. If I understand the core concepts of animation, I look for the same tools and general workflow within another animation program. This may be understanding how keyframes work and timing, or how I can animate a rig.
If I know how to move/rotate/scale an object in Unity then I'll look for similar tools in Blender. Learning new concepts can be quite difficult if you have nothing to compare it against. You won't always find a similar concept or tool in something new that you're learning, but whenever possible use this a a guide to help you learn at a quicker rate.
Keep It Simple Stupid
KISS (Keep it simple stupid) is a common expression and it's quite practical in many aspects of life. In programming there is a similar expression called YAGNI which is short for You Aren't Gonna Need It. In programming it's common for programmers to want to build a ton of functionality.
Building systems that allow us to extend and add more if need be, when really we spend way more time building the systems than actually finding uses for them. When prototyping a game it's often quick and dirty in a technical sense because the goal of the prototype is not to have a polished and refined game but rather to test out what works and what doesn't.
It's a huge waste of time to build an intricate environment with textures and lighting, just to see if a character can run and jump over generic obstacles.
This again goes back to the 80/20 rule because many of us want to get a lot done. Some people want to create one render a day, others want to add more and more to their artwork. They want bigger and better and while that may sound great, creating something smaller and amazing would yield better results, quicker.
Lately I've been toying around with the idea of the "casual" and "hyper casual" games. These are games that revolve around a very simple mechanic; often just a single mechanic. Think about games like Flappy Bird and you get the idea. Games like that are incredibly popular. They're easy to get into, gameplay is simple to pick up, and they're usually addicting.
I've recently started experimenting with a new game called Tank Ball. The idea is quite simple, you play as a tank that can only rotate its turret and shoot. You can't directly move the tank, but shooting provides recoil force that moves your tank in the opposite direction. Tanks shoot out balls that ricochet and can damage other enemy tanks.
By keeping to this simple mechanic I'm able to focus on refining it and making it feel better rather than trying to add more complexity to it. I've nixed the idea of adding power ups or shields. Also decided against any kind of inventory system. Even though it's a very simplistic mechanic I find myself finding a multitude of ideas on how to use this mechanic on a variety of different levels.
Adding in restrictions, whether it's voluntary or required, can force you to be more creative. If you had to model a vehicle, but had a strict limit on the amount of tris you could use, it would force you to simplify. You may find that you learned a lot more modeling in that way than if you had unlimited freedom in how dense the mesh could be. As the saying goes Necessity Is The Mother of Invention.
Do Less, Better
Bottom line: aim to do less, but better. Instead of trying to create an amazingly detailed character in one day, why not just focus on creating an amazing head in day one, the body next, then hands, etc. Focus on the quality of your work versus the quantity. There's always a need for quality work in the world.
If you were not aware of the Pareto Principle prior to reading this you are now, and you'll start to see its benefit in every day life. Learn how to harness this power for your own good. You may find that you'll work less while become a better creator because of it.