I was recently interviewed for the Everyday Innovator podcast. This is a great podcast that interviews leaders in the product development and product management field. I’m honored to be included in the podcast.
Excerpts from the interview:
Our guest for this episode is Montie Roland. Montie used my online training course to prepare for, and pass, the New Product Development Professional exam, earning him the NPDP certification from PDMA, which is the oldest and most established professional group for product managers. After passing, he contacted me to discuss providing training to product managers in his company. This is a topic I always enjoy because I love helping organizations improve their product management capability and helping product managers further their skills and how they work with each other and the product team.
As I talked with Montie, I also learned about his background, became fascinated by his experiences, and knew he had to join us here to share his stories and knowledge.
Montie has pursued an entrepreneur path, building his own company, and an intrapreneur path working in an established company. He is a mechanical engineer with a ton of design experience.
We talked about his experiences, including the pros and cons of working for yourself vs working for an organization.
[3:19] What is your current role as an intrapreneur?
I’m on the new product development team at Pentair. If you’ve ever been in a swimming pool, the water probably went through one of our products. I get to do a lot of front-end work in industrial design and the connection between customer and product. The strongest part of my skillset is bridging that gap, and I have the chance to do it on a lot of different projects in a large organization.
[5:26] What kind of products did you create as an entrepreneur?
I ran Montie Design for about a decade. We started in B2B products and eventually moved into B2C. We made rack-mount servers and packaging electronics. Clients would come to us because they were trying to get around politics in their company or were behind schedule on a project. We developed products that they could transition into manufacturing. On the B2C side, we made in-home air filters that were highly stylized. We tried to make as much as we could locally so that there was a community feeling to it. We wanted people to look at our products and say that’s the way they would have made it themselves.
[13:02] What are the advantages of working on your own?
I enjoyed the sense of self-determination. You don’t have someone looking over your shoulder like you do in a big corporation. You can explore directions that you might not be able to otherwise. People who work in product development have an inherent sense of adventure, which tends to be more constrained in a corporate environment.
[14:40] What are the disadvantages of being an entrepreneur?
It requires a lot of work. If you have a spouse or family, you need to have buy-in for your entrepreneurial endeavor at home. You also need to have the funding you need and scale your operation based on the funding you have. I had a great time working on my own, but went back to the corporate world because I needed a lifestyle change. I scaled my business back as a result and now do Montie Gear on the side.
[20:45] What are the advantages of working for an organization?
I’m part of a large, multi-disciplinary team that has a lot of depth. There are times when you might have to switch projects and hand off what you’re working on to another engineer who is a better fit. Pentair fosters the sense of trust necessary to make those transitions happen. It’s also much closer to a 40-hour work week and I don’t have to worry about everything. I have a lot of people around me who are experienced at product development, which pushes me to keep my skills sharp. My colleagues and I challenge each other, which creates a very collaborative environment. I get to focus my time designing things and don’t need to worry about all the other aspects of running a business.
[25:55] What are the disadvantages of working for an organization?
There’s a lot of skepticism from companies about hiring entrepreneurs because they think you’ll get tired of the corporate environment and be out the door to do your own thing in six months. Look for companies that see your entrepreneurial background as a benefit because you can bring different skills to the table. It’s also difficult for HR to translate entrepreneurial skills into existing roles and job levels. You need to be flexible about starting at a lower rung and working your way up over time. Another disadvantage is that you’re not responsible for every decision; the scope is much smaller and you need to be okay letting go of some responsibility. There’s also a culture shift because every company’s culture is different.
[32:58] Why did you pursue the PDMA NPDP certification?
It’s easy to back off on training and certifications when you’re an entrepreneur because you’re so caught up in the day to day of running the business. In a corporate environment, you have time and money for professional development. The company wants you to grow and that makes it really easy do things like certifications.
“A candle loses nothing by lighting another candle.” – James Keller
Thank you for being an Everyday Innovator and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below.
Montie’s Note: Here is a Montie Gear product story that gives a insight into the design and a use case that includes testing and field use by the designer. This was a customer newsletter item.
Fall is synonymous with whitetail deer hunting in the South. Our wives become “deer widows” for 2-3 months while we disappear into the woods and look for that giant buck we’ve been watching for. Wives get used to seeing their husbands up late at night looking a pictures from trail cams and learn to cook venison. Saturday mornings are viewed from 20 feet up in a tree stand. Good times and priceless moments.
The Hunter’s Friend was initiated by a suggestion from Al Davis, owner of AllFab Solutions. He is an avid hunter and wanted a way to hang his bow or rifle from a tree without having to run a screw into the tree and damage the tree. A few weeks later, the Hunter’s Friend was born.
Getting your gear to the field and into the tree stand means work. Gear that you take up to the tree must be compact, lightweight and easy to deploy. Setting up your gear while you are hanging from a tree and 20 feet up means it must be well designed and flawlessly task at hand. Anything else is just something that will get left at home.
The Hunter’s Friend holds your bow (or rifle) in the ready position. Holding your bow, or rifle, in your lap can be tiring after a few hours. The Hunter’s Friend solves that problem while keeping your bow at the ready position. I also use it to hold my calls, binoculars and range finder. It straps around the tree without damage so you keep the landowner happy.
I believe that we have 3 in stock so don’t delay in ordering yours, or suggest it as a gift. Check out the pictures below from a recent hunt in Chatham County, NC.
Do really like your Montie Gear slingshot, AR-Rest or other product? Help us tell the world about the Handmade, Heirloom Quality products that we make right here in NC!
Reviewing your Montie Gear product is a great way to give potential customers access to your opinion before they buy. We’ve streamlined the review process to make it quick and easy for you. Please a take a few minutes and review your Montie Gear products by going to www.montiegear.com, logging into your account, navigating to your favorite Montie Gear product at www.montiegear.com and then click on “Add Review”. Once your review is submitted, please email me at email@example.com and I’ll email a coupon code good for 25% off your next purchase!
Our philosophy for Montie Gear products is pretty straight forward. We provide “Heirloom Quality Products That are Troublesome Gap Tough”.
Many products in today’s world are meant to have a limited life time. A good example is that cell phone that you need to replace every two years. It works great, but over time technology changes and the fragile electronics have a limited lifetime. We want to design and sell products that have a very long lifetime and may actually get passed along to your kids or grandchildren. Many rifles get passed along from parent to children, sometimes marking a rite of passage. Granted a shooting rest isn’t as special as your Grandfather’s rifle. However, we work to design and sell products that are simple, elegant and high enough quality that you will want to pass them along to your kids or grandchildren.Troublesome Gap Tough
Troublesome Gap is a place in Western North Carolina, near the peak of Hap Mountains and overlooking Spring Creek, NC. My parents purchased the property over 40 years ago. I grew up spending time there. We cut firewood for heat, picked blackberries and raspberries, and spent some great weekends up there. Troublesome Gap is remote and rugged, the prefect place to test our products. Troublesome Gap Tough means that the products are rugged and easy-to-use. A delicate, hard-to-use product is a liability in the field, so we avoid that by making sure all our products provide a great customer experience and are built to last, even in demanding conditions.
As President of Montie Design, I am proud the fact that we are shipping high-quality, U.S. made products. I am also proud to be an American.
Can you get so Lean (Lean Manufacturing) that you get lost in the process? You bet you can.
Lets talk about the Kano model. The Kano model helps you to organize your product development and management efforts between basic expectations, performance enhancements and delightful additions to your product. Understanding the difference and applying this model to your product management and design management ultimately serves as a reminder to not forget the joy of creating delightful products that please your customers is great ways. Don’t end up getting lost in the process and forget to delight your customers.
Forget about designing from a clean sheet of paper. It can’t happen. The designer himself prevents brings a tapestry of experience, skills and preconceptions with him. Embrace that diversity and create better designs, even when you are starting from scratch. Once you understand you, then you can think on a broader scale and truly innovate on your next project!
This is a podcast I originally created in 2012.
Audio File Transcript: Who Are You and What Does that Mean
Hello. My name is Montie Roland. And I’m with Montie Design in Morrisville, North Carolina. I wanted to spend a few minutes with you this morning talking about who are you and how does your skillset, your drive, your . . . how you go about creating new product concepts or new product ideas; how does that fit into everything.
We all have our own desires, drives and I want to kind of go through it and talk about it. And maybe learn a little bit about each other as we go through it.
I’m the president of Montie Design and also the president Montie Gear in Morrisville, North Carolina. Montie Design is a product development firm. And we develop products for you. And we fill in gaps. Sometimes it’s a small project; sometimes it’s a large one. And what we do is fill in those gaps in your engineering or your industrial design or your prototyping department; fill in those gaps to help get your product to market.
Montie Gear is a company that provides outdoor shooting equipment, and slingshots and fun stuff. Montie Gear was founded about four years ago as one of those things we decided as an institutional learning tool. And we decided that we wanted to design some of our own products, not just everybody else’s. So we did a couple and then said, well, what would it be like to sell them? How do we sell products without spending a lot of money on advertising? So, we put them on our website, Montie Design website, and then we also came up with the idea – thanks to Carl – of doing a lot of test and evaluation units. And over the years that test and evaluation unit approach has even rolled into a service we now call Social Reviews. And so, I don’t want to spend all day talking about that. Something we’re proud of. Montie Gear line has grown from zero to over a hundred thousand dollars in sales in about four years with very little advertising. So we’re very proud of that and we’re proud of the products we sell.
So it gives us a little different perspective on the product development process. So, not only do we develop products, we also are responsible for some of those products for selling, and manufacturing them. And that’s also kind of spilled over in that we’re now doing that for two clients where we’re providing the backend services – they sell them, and we ship them. We make sure they’re manufactured, that they’re packaged, they’re QC’d and then the customer’s happy.
And so, first question, our first thought is I want to throw out the thought of, you know, who is Montie? Who am I? If I’m going to tell you how other people are, I’m thinking maybe I should go ahead and kind of do a little analysis on myself. Now, Montie Design designs products for a wide variety of situations – manufacturing approaches. We have products that we design – they’re going to go straight overseas. We have products that we design and we get to a certain point and we turn them loose to an ODM somewhere the other end of the Internet and they take it from there; and we read about it in a magazine. We other products we’re more intimately involved with throughout the whole lifecycle. But, you know, it comes down to the “Who’s Montie” and how I think. I think the best example is to maybe watch what I do and not what I say in this case and look at Montie Gear.
With Montie Gear we’ve come at it from the standpoint of we want to have a high quality product that’s what we call heirloom quality-Toublesome Gap tough. Which means a very robust product that’s going to perform well in the field and it’s going to be the kind of product that you want to give to your grandkids because it’s that lasting and hopefully timeless.
So, right there, you kind of have to ask, well, how many of those products are high-volume. And the answer is very few. So we have mainly products that are low-volume, low-capital requirements – and by low-capital requirements, we haven’t built a lot of tooling; we haven’t spent a lot of money to get the products to market. Now the trade-off with that, of course, is the products cost more to manufacture, so you have a higher quality product, higher cost of goods sold, but at the same time that fits in with the Montie Gear approach where what we want to have is this heirloom quality, made local, products.
So, when I go to create a product for Montie Gear, or work with someone on our team that does, or work with an intern or what have you, we’re definitely in the mode of Let’s-get-something-out-there-fairly-fast, without spending a lot of capital investment; without a lot of investment. So, we want to design it, have it work well, but not rely on the fact that we’re going to injection mold it to get the price down or what have you; die cast it, and have to sell gazillions instead. We’re going to plan to sell handfuls at a time. So, in this case, my natural instinct is to rely on local manufacturers for Montie Gear, and to work with those local manufacturers closely to have a higher quality product sold at lower volumes – higher cost, but at the same time the higher quality and also that emotional appeal of having a product that the down the street made (which I think is having more and more value in our society). At the same time, if we’re going to have a higher-end product, we need to provide a higher level of customer service as well. So what we want to do there is to treat that customer well and make sure that we meet their needs on a timely basis.
So if we take that a little farther and look at it in a broad perspective, there’s several different kinds of companies. One company is a company that’s service excellence. They may not be terribly innovative, but you get the same service every time. A great example of this is McDonald’s. You know what you’re going to get no matter where in the United States you go; and to a certain extent, you’ve got a good idea of what you’ll get no matter where in the world you go. So, their goal is to bring you a reliable product at a reliable price, and get it to you quickly and have no surprises. So, it’s a safe bet. You stop and eat at McDonald’s, you know exactly what you’re going to get. That’s not a terribly innovative company at this point. It may have been innovative early on by driving the concept of fast food and so forth. But at this point, it’s a mature company and they don’t do a lot of innovations. They do little tweaks here and there. And they definitely don’t create a lot of new intellectual property; at least, that goes into their products. Most of the intellectual property goes into logistics, service.
So let’s look at other companies that have to innovate. So, kind of break it down into two different types. One is a product excellence company. So a product excellence company is a company where you know that you’re going to get the finest product you can get. You’re going to get a high quality product; you’re going to get service to go with it. So, the whole experience is excellent. They may or may not be innovative, but at the same time, you’re going to get this high quality, high satisfaction product. A good example is that you may go buy a ring for your wife (or your husband); and that ring hasn’t really changed a whole lot. You got a little filigree here and its silver instead of gold, but for the most part, your expectations is very high level of quality. Not a lot of innovation in that industry, I would argue, for the most part. There’s some artistic work but not a lot of what I describe as true innovation. And then another example is a company that’s very innovative, or it could also be very inventive, where they create new intellectual property. And so, in either situation that organization is relying on either innovating or inventing to drive their products ahead of their competitors. And that’s a very important part of the whole ecosystem as well. And that’s the ones a lot of times we tend to really want to get behind. And everybody just wants to always tell the example of Apple, but they’ve come up with some really great products by often by innovating and inventing. And so they’re an example of a company where they try to stay ahead of the curve. And a good example of that is if they don’t, they’re products don’t always compete as well because of cost. So, they want to have this innovative customer experience, these innovative products; but as those products age, there are a lot of times that “me, too” products are a lot more attractive. A good example of that is the iPhone is now starting to be displaced by other smartphones, where at first they were “me, too” – for example, Samsung, HTC – but now they’re starting to actually have some innovation and some invention in what they do. And so they’re competing very well. And if you look at the iPhone 5 versus the latest HTC or the latest Samsung, there’s starting to be a technology gap, which in this case isn’t in Apple’s favor because they really relied on having this amazing edge in the marketplace. Now, they also have a lot of other things going for them, but in the realm of phones, that edge is absolutely critical to maintain their market share.
This also applies to smaller organizations. I like going to the Apex farmers’ market. And there are several folks there that cook different types of items. So, one example is there’s a lady there that makes pies and she makes muffins and so all the recipes she’s using are pretty old school. There’s not a lot of innovation. So, what she’s bringing to her product is quality; its handmade from scratch; these very desirable elements, but there’s not a lot invention or innovation that goes into that. So, if you look at this in the context of the three categories I described earlier, she’s in the service excellence category, or product excellence. So, she’s using her time buying some materials and turning that into a product. Now, in no way am I denigrating that as a model for business. There are a lot of very successful businesses that do that. Think about how many large cookie companies there are. And so, it’s a very valid way of doing business. I think the important thing is that if you’re in that type of business, it’s often handy to understand what your model is to help you make future decisions and current decisions.
So a lot of the folks that we buy stuff from that make pies and pastries at the farmers’ market, there’s just not a lot of innovation there. So, they want to provide a high quality product; they want to provide a friendly face; and it tastes good. You like the fact that the person you’re talking to made it yesterday or this morning, put their time and love into it. And so that’s a good way to look at that. The other categories you find in different places. So, for example, if you’re an inventor, then generally when someone considers themselves to be an inventor, or we consider them to be an inventor as an organization, they have an interest in creating intellectual property, and then selling the concept. So, they’re truly inventing. So, in this case, they’re viability as a service provider (or as a vendor) to someone is their ability to innovate. So, they fall in that last category because if they come up with a concept that’s already out there and it’s a “me, too”, as an inventory they really haven’t invented anything. When you look at entrepreneurs, the entrepreneur – and I want to define the inventor as someone who invents for the sake of invention-to-license later – an entrepreneur is someone who builds a company and an infrastructure that is designed around selling a product; manufacturing and selling it. It’s an important distinction.
So when the entrepreneur does this, the entrepreneur may be making pies to sell at the flea market; may be making cupcakes; and in the last few years there’s been this huge amount of cupcake industry forming. It’s really amazing how many cupcake companies there are. These companies that make cupcakes make some amazing cupcakes sometimes. So you can go and get a cupcake at the grocery for $2.50; or you can go to a specialty store – you might get a $20.00 cupcake. Yes, a $20.00 cupcake. So, could a cupcake company kind of fall into these categories? Well, yes. A cupcake company could be a matter of picking twelve existing cupcake designs, styles, and then making those. And in that case, their appeal is service. They’re providing a product that’s based upon their labor. So it’s not a real inventive product in that case. But there are also cupcake manufacturers and cupcake stylists that provide cupcakes that are very different. And they’ll actually do research into different ways that they can do this. Or maybe come up with their own. So, there may be a new style of icing or a new style of . . . packaging. You know, what can they do different that sets them apart? Now, the question to ask is – Are you selling cupcakes because you have something that’s truly original? It’s a, I don’t know, vacuum-puffed cupcake that no one else can do. And you’ve got this trade secret on how to make vacuum-puffed cupcakes. Or, are you selling products that are just based on your hard work and love? And usually there’s a mixture of the two. But, so, it’s important to understand how your business thrives based on where you are in these models. Because then, all of a sudden, you can make better decisions about how much time and resources and money you should put into these different activities. So if having inventive cupcakes doesn’t drive sales, then maybe you’re putting too much effort into inventing those crazy, new technology cupcakes. If the fact that you sell these crazy vacuum-puffed cupcakes is what is driving your new sales (or your existing sales) in a big way, if that’s what’s driving your growth, then maybe you need to put more effort into the crazy ones.
And so it goes a little beyond just the matter of the accounting; saying this cupcake sold this many, this cupcake sold this many. I think it also goes into the strategic planning. So I think it’s important to plan your strategy around what type of company you are. And so understanding these distinctions and where you fall, and how where you fall helps your business grow, is very, very important. This type of strategic planning and understanding is important at the Fortune 500 level; its important at the small business level. Because it important for anyone in a small business to make sure that you’re always, always – always – making good use of your resources. And understanding, you know, your place in the process of developing new products; or not developing new products helps you make the best decision to maximize your return on investment. Which is critical because it’s a small business; it’s tough enough to survive even if you’re making good decisions. So, making better decisions may be a different between subsistence and true growth and just kick-butt kind of company. And I think how you go about product development, or don’t, is an important part of that and can help you dramatically.
I hope this podcast is helpful. This is a tough subject to sometimes kind of articulate through and work through and walk through with you. So I hope it was helpful. Understanding your spot in your strategic model and what the strategic value of your . . . or what the value proposition of your company is, is something that can really help.
Let me know if you have any questions. Montie Roland, Montie Design. (M-O-N-T-I-E)@montie(M-O-N-T-I-E) .com. Visit us on the website – (M-O-N-T-I-E)@montie(M-O-N-T-I-E) .com. There’s a handy little chat tool and you can click on it and get immediate help. Either way, it’d be great to hear from you. And have a great day. Montie Roland, out.
10 years ago, the push was to go paperless. Is paperless too much of a good thing?
Data in your computer is passive. Yes you can manipulate it, share, mine it but you have to go ask for it. Why not make data active?
Lean Manufacturing techniques include tools to make your data active but getting it out in from of your employees and managers on daily basis. Put that data in front of your team an understandable and actionable format where it does the most good, i.e. right in front of them.
Lets explore the various facets of active vs. passive data. Comments and suggestions are welcome here or at firstname.lastname@example.org
Here is the transcription from the podcast………………………………………………..
Audio file: 2015 May 17 – Lean Thoughts 1 – Active vs. Passive Data.mp3
Time transcribed: 12:29 minutes
Hi. My name is Montie Roland. I’m with Montie Gear in Apex, North Carolina.
What I wanted to do is to share some thoughts with you today and have at least a one-way dialogue – it could become two, if you email me – about the difference between passive and active information. So I’d like to spend a few minutes talking about that. And maybe define it and have some examples.
One of the things that’s happened over the past twenty years is that we’ve had this head-long rush to get everything on the computer. So, we assumed that getting it on the computer is more efficient; is more cost-effective; is safer because you can back it up. And so we’ve created database after database after database. And one of the joys and the beauties of – and potentially harm – of doing this is that everybody can have access to information, without having to go down the hallway and grab something from a file cabinet. Now, of course, the horror is that can be hacked. Someone can get into that from across the world. Whereas, a file cabinet, you’ve got to physically be there to get into it. Now, a file cabinet can be broken into as well, but someone on the other side of the globe isn’t going to be able to do that without visiting here. So, we’ve created this electronic database that contains what we do. And the beauty of it is that everyone in your company can sit down, and if they have the right software and they have the access, they can read that data. The problem is that they have to go read it; they have to go look for it. So I’m going to call that passive data. Now, active data is data that’s right up in your face. And for those of y’all that are family with lean, you’re going to start going “Oh-ho, this is exactly where he is headed” because with lean the goal is to use vertical surfaces as . . . well, I shouldn’t say the goal. Lean is going use boards, charts and effectively, use your vertical surfaces as a way that in an instant you can look at a chart, and have an idea of that particular part of your business and what’s happening in there. And so in lean, there’s a lot of different charts and you chart different areas. And so the idea being that in seconds you can know what’s going on. So, let’s throw out an example. So, one example would be if I have a database of a soccer game. And what I’ve done is, through the magic of the computer and a vision system, I’ve tracked where the ball is, where the people are, what their speeds are, how fast they’re moving, how fast the ball is moving, how . . . blah-blah-blah. So, I have this giant database of excruciating detail regarding the performance of every player on the field. And somewhere in there I have the fact there was a goal scored at this point – point-oh-oh . . . twenty-seven minutes, three seconds and two milliseconds, the ball entered the net. So, if I want to know what’s happening in the soccer game, now I’ve got to have a way to visualize all that data. So, I’ve got to go to the computer; I’ve got to use my visualization tool; I’ve got do all this stuff. But the beauty of it is if I want to know what that player’s performance is, or that team’s performance is, I can do that ad infinitum. Now, let’s make a contrasting example. So, I’ve got the computer database with all this wonderful information. And then the contrasting example is I go to the game. So at the game, there’s several key elements involved – there are players on the field; there’s a ball; from where I’m sitting, I can see the ball. There’s two goals, there’s two goalies (or a football, for our European listeners). And so, I’m in the stadium. I can see the scoreboard. The scoreboard gives me a few pieces of information – what’s the score, what’s the time remaining in the half, what’s the, you know, which half are we in. And so, those pieces of information are there. I can see the ball moving. I can see the ball going in the net. Well, maybe I’m not sure. Did it miss the net? Or did it go in the net? Oh, I look at the scoreboard – boom! So, by going to a soccer game, I can instantly know what’s going on from anywhere in the stadium. So the beauty of it is that I don’t have to have a visualization tool; I don’t have to bring out my computer – it’s all right there, between the scoreboard with an absolute minimum of information (but the right information) – and – watching it unfold on the field, I always know what’s going on just by a glance. Whereas if I monitor this on the computer with this huge amount of data, I have to go to the computer; I’d have to figure out to get what I want and so forth. Now, I think it is important to, you know, throw out there, that you can have a visual board on the computer. I’m going to make the argument that the difference between something you printed this morning and what’s on the computer, effectively if the data is current, it doesn’t matter. And the beauty of printing it on the wall is that someone can walk by and in an instant and see it. And you’ve got a lot more wall space than you have monitor space.
So, yes, there are lean set-ups where people put their display, their information, on monitors. Now, that means you’ve got to bring that information into that display. Maybe it’s automatically from other systems. But the idea is that active information is something that you can glance at and get an answer. You may be glancing at a giant monitor; you may be glancing at a color print-out or a black-and-white print-out that’s hanging on the wall when you walk in the building. But one of the things you see with lean – and lean being, you know, the popular name for the Toyota manufacturing system, is you see active information that’s organized and updated, and that active information lets you know what’s going on. And is a way of communicating what’s going on in an instant because you look at a chart, you know what to look for, you see the colors, you see the ways that everything’s laid out. So now, in an instant, you’ve been updated. Which is a great way to communicate.
So, the opposite of that is passive information, where you’ve got to go to the computer, sit down, look it up on a spreadsheet or look it up here, or do what have you. And so, I’m going to make the argument that where you can use active information, you’re in a much better position because someone doesn’t have to spend the time to go look it up; and also, someone can walk in, know what they have to do, have a constant reminder of where they are and what they’ve got to do; how things are going – because it’s right there and that information’s available. That helps everyone in your organization make better decisions because they’ve got the information they need, and it’s timely and they can make decisions that are timely. And every day every employee makes thousands of decisions. So if you leave them in the dark, they’re guessing at what’s best for the company. If you inform them, give them a structure, educate them, and, you know, lay this all out, now, all of a sudden, those thousands of decisions can be decisions that are the best, the ideal ones, that help get the product out the door quicker with high quality and conserving resources.
So, that’s why I think understanding the difference between active and passive information’s important. And then, also, putting that understanding to use in terms of getting that information to everyone. Now from a Montie Gear perspective. So one of the things that I’ve been thinking about as I’ve been taking my journey into lean is how to implement that in a small company. So, maybe that’s a discussion for another time. But I hope that this has been a good bit of information for you. Give you a little better understanding of that difference between active and passive information, and why it can be so valuable to give your employees the information they need to make those good decisions all day long, every day. Because they’ve got the information they need and then they can act on it.
Join me as I chronicle my journey into lean manufacturing! This is part 1 of the series. Comments and suggestions are always welcome at email@example.com.
Here is the transcript from the podcast……………………………………
Audio file: 2015 May 17 – Lean Thoughts 0.mp3
Time transcribed: 15:50 minutes
Hello. My name is Montie Roland. And I’m with Montie Gear in Apex, North Carolina. Today, I’d like to spend a few minutes and talk about my journey into Lean, and what I’ve learned in the past few months.
So, let’s back up and let’s talk about, you know, what is lean? Lean is a popular name for the Toyota manufacturing system. Toyota has spent a lot of effort and time and intellectual capital in developing a state-of-the-art way to make cars. The Toyota manufacturing system is the model for the rest of the world. When you hear someone in business talk about that their company is lean, or they’re going lean or what have you, it’s about putting into practice that basically leaner, a version of the Toyota manufacturing system.
Toyota has a really, really, really well-thought-out way of making cars. And this applies to other segments of their business as well, not just manufacturing. It applies to their . . . to their dealerships; it applies to other areas that are ancillary to their manufacturing of their cars. They’ve got to sell them; they’ve got to service them. And so, as I understand it, the principals of lean and the application of lean has been put in place by Toyota throughout their entire system (as far as I know). I know that dealerships put it in place. They definitely put it in place on the manufacturing. And so, it’s important to have an understanding of what “lean” is.
So one of the guidelines behind lean is that you want to optimize your process. Now, a lot of times when you’re talking to someone about lean, first thing they say is, “Well, lean is about reducing waste.” And so, when someone says that and looks at you, you should say, “No! It’s not. It’s a by-product of lean, is reducing waste.” And you get a . . . sometime they’ll maybe tilt their head, look at you, and go, “Well, no. This is . . . in lean, we reduce waste.” So, I want to make the argument that in lean you’ve got two directions that you can do optimization; two main directions – you can always optimize, you know, a lot of different ways. But, there are two main directions that you can optimize for. One is that you can optimize for resources. So that means that you can try to keep everybody busy; you can try to make the best use of space; make the best use of materials; make the best use of personnel; keep your per-unit cost low. And that’s a good thing. However, the challenge with that is that you end up inevitably, by optimizing for resources, you end up developing silos. And by a silo, what I’m talking about is that if you’re, let’s say, the person that assemblies widgets; then, your pay and your bonuses may be directly driven by how many widgets you build. Well, and that’s fine until the point where the person who takes your widgets and ships them can’t keep up. At that point, you may be making widgets, but they don’t have the capacity to ship; or maybe the capacity to sell. So at this point, you’ve got an incentive to continue making widgets because if you’re not making widgets, well, you’re efficiency goes down. And when that efficiency goes down, your incentive goes down. So, now we have a problem because you can imagine that even if it’s not this severe of an example, every group is going to be evaluated based on that group’s performance. Well, when you do that, that’s great; what you’ve got to watch out for, though, is does that group’s performance help the company as a whole. And so they may be amazingly efficient – but – something they’re doing is the part of being so efficient may make someone else inefficient. At that point – mmm, maybe you’re not doing the right thing.
So, this is a natural outcome of building silos and optimizing for resources. So in lean you’ve got to do more than just optimize for resources. What you’ve got to do is you’ve got to optimize for flow. So when you optimize for flow, you have to establish communication between groups. Now, you may have a corporate culture that is absolutely wonderful, where people, you know, talk; they communicate. And everything is wonderful. But a lot of times you have a lot of communication within your group (whatever that group is – manufacturing, shipping) but a lot of times you don’t have communications, let’s say, with accounting. So, if want to optimize for flow, you’ve got to communicate. And that’s the first challenge. And that’s one of the things that lean really tries to address is that communication.
So, let’s talk about optimizing for flow. And what does that mean? Well, when I optimize for flow, I want to optimize for the speed at which I’m adding customer value. What that means is that when I get an order, I want to get that order in this customer’s hands as quickly as possible. Because when I get it in their hands as quickly as possible, then the customer is happier; more delighted or more satisfied. And also, I get paid quicker. So, I don’t have money sitting around in inventory or work-in-progress or what have you. So, lean is all about a customer pull. So, you know, the customer’s making an order – or – we’re filling to maintain an inventory – either one – but we’re going to refill that inventory after its depleted, so you want to refill it as quickly as possible. Or we want to ship as quickly as possible, depending on how the expectations of your customer are and how your industry works.
So what we want to do is we want to get that product made as quick as we can, get it out the door, get it to a customer, and, of course, that being a high-quality product that we made in somewhat an efficient way. So, now you can see what’s at odds is that the most efficient way when it comes to resources may not be the quickest. Now, I want to point out an example. Let’s say that we have four people making slingshots. And let’s say each slingshot takes a month to make (for one person). But let’s say that four people can make a slingshot in five-point-two days. So in this case, if I have four people working on a slingshot at once, there’s some inefficiency because four people have to work together, shared resources, what have you. But, I’ve got the capability to make one slingshot at a time, instead of four at once. And so, the trade-off is that if I look at the folks that make those slingshots and I say “You get paid by how many slingshots you make a month”, then they’re going to say “Well, I’ll make slightly more if we work on them separately”. But then, the trade-off is that it takes a month for one person to make a slingshot. Now, let’s say that I have four people making slingshots and it takes one-point . . . one week and an extra four days, or one month and four extra days to make four slingshots, but I do them sequentially. So, now I’m kicking out a slingshot at just over a week; so a little bit over every week I’m getting a slingshot out the door. Little less efficient – but – now all of a sudden I’m getting it to my customer quicker; I’m getting paid faster. So when you think about, you know, work-in-progress and inventory, that works out well. But it’s not quite as efficient. So if I organize for efficiency, then everybody’s going to want to make one slingshot per person. Or, excuse me, for resource efficiency, everybody’s going to want to make one slingshot per person. If I say I want to get these out as quick as I can, then I’m going to have all four people working on that slingshot, kick that slingshot out; now, I’m shipping a slingshot in a little over a week. So every week, almost, I’m kicking a slingshot out the door. And so this is one of the conflicts that built into lean. So, we want to be efficient and lean has a lot of tools to do that, but lean recognizes right off the bat that you can never be one hundred percent efficient because you also want to optimize for flow. If we’re a hundred percent efficient then the delivery time goes up because of multitasking, because waiting . . . it gets, you know, your deliver time goes up exponentially, not linearly, as you work on multiple things at once. A good example with our slingshots, is that let’s say that it takes a week to ship four slingshots. So now I’ve had four people working on slingshots for a month, and I’ve had . . . or I’ve had one person . . . or excuse, four people working on one slingshot at a time – well, now all of a sudden, if I had limited shipping capacity, then it’s important to not overburden that shipping capacity by forcing them to ship all four slingshots at once. Whereas, if I could spread that out, it may be that I have to have a fourth less people in shipping to ship slingshots, because I’m shipping one at a time, not four at a time.
This is definitely a very arbitrary example, but you kind of get the idea of this . . . dichotomy between optimizing for resources and optimizing for flow. And I think it’s a really important because if you consider lean just purely making your company more efficient then you really aren’t doing lean. You’re not. Lean is about monitoring your process. So, when we go to the next step here is that how do we optimize these things. Well, lean is not as much about the outcome as it is monitoring the process, and improving the process by everybody constantly improving. And so, when you think continuous improvement, you know, well, okay, that means people learn how to make widgets faster. No. Because at some point, a person’s going to sand a corner down only so fast; there’s no . . . that is going to peak, in a way. So instead what we want to do is monitor those processes so we know what’s happening. And so lean is all about monitoring the process, and by monitoring the process and educating the workforce and getting the workforce involved in monitoring, then all of a sudden, as a by-product, everybody’s making better decisions that improve productivity. So, I think that’s a really, really important part of that.
Well let me leave you with this for now. And I know I’ve kind of talked a little bit about lean, but it’s kind of a really neat way to run your business. It’s not a simple thing; it’s an all-encompassing thing. It’s not a couple of charts on the wall. It really is a way to run your business from stem to stern. Lean is not a partial change. It’s a culture change. Without the culture change, then the effectiveness of the lean efforts are dramatically reduced.
Well, Montie Roland, signing out. Have a great day. Bye-bye.
Audio File: 2014 Feb 12 – Giving The Go Ahead To A New Product.mp3
Audio Length: 10:10 minutes
Hello, my name is Montie Roland with Montie Design in Morrisville, North Carolina. We’re a product development firm with core competencies in mechanical engineering and industrial design.
One of the interesting things that happens working with clients from bigger companies or medium-sized companies – or even smaller ones that are, you know, are growing – is that we’ll design a . . . whatever. And so we’ve designed this project, we’ve gotten to know our contact at that client, and one day after a design review that client looks across the table and says, “You know . . . I’ve got some stuff I’ve been working on in my basement”. It’s interesting that it’s very likely for a client that’s in charge of – or enabling; in charge of, also – product development for his company often will have something that they do on the side. And it’s interesting; so they may enjoy their job and they work very hard at it; at the same time, when they talk about the thing they’re making in their garage, there’s usually this big smile. And so, then what happens is they look at us and say, “That’s why I respect what you did so much with Montie Gear; because I know how tough it is”. And Montie Gear’s our product line that we created four years ago of our own products. We manufacture them; we sell them; we distribute them; we maintain the website . . . well, Daniel helps us. But, so it’s our own products, though. And it’s become kind of this company fascination. But, we’ll have clients that have this emotional connection to our Montie Gear products. Maybe it has nothing to do with the products; it’s just the fact that they really like coming up with new stuff. And so they see us doing it and having a good time and it’s a common situation that we’re both having a good time doing new products.
And so, there’s a couple of thoughts I want to throw at you. And we’ll talk about it from the perspective of an entrepreneur, but this also can apply from the perspective of a big company. Because, if you look at a big company as an organism, some of the same thought processes, many of the same thought processes, apply. They’re modified in some ways but, at the basic level they’re pretty similar.
So, one of the first thought processes is to go after the whole enchilada. It’s go big or go home. Well, the good side about that is that if you go big and you win big, then you profit big. And so, that’s a good thing. So if you go for a product where you’ve stretched what you can do or what your company can do, and it’s a product that can change the market or can take over a market or can grab market share, then Woo Hoo! That can be a big winner because the upside to that is that you can have some big profits. The downside is that you’ve invested a lot in it and you’ve also not invested in other products. Now, form an entrepreneur standpoint, we’ve had one single owner, single employee companies where the owner of the company said, “I’m going to do this. I’m going to go big. I’m going to injection mold this. I’m going to sell these all over the country” and, you know, “Either help me or get out of my way”. And so, the one I’m thinking about at this moment had the funds to back it up. He had the money in the bank to do what he needed to do, and so, he wrote checks. We helped him out. He did other stuff and now he’s got a product that’s starting to take off like crazy. So the upside is going to be huge for him, I think. Good product. Great salesman. Good attitude. Thinking about the business. And thinking about, you know, how he’s going to make all this happen on a big scale and, hey, let’s . . . we helped him push.
And so, we have other clients – and like I said, this can apply to an entrepreneur or to a company – where they’re not in a position yet, for whatever reason, to go for the big score. And so for them the medium-sized score or the smaller score is a much better option. Maybe because of cash flow; maybe because of other resources. Maybe because of time resources. Maybe they’re very business doing something else. So if they go after this major product, then it may take years to get there because they got so much on their plate. Well, the other possibility is to go after a bunch of smaller products, or smaller, I should say, lower effort products. And, then that gets them into that new market. That gets them experience in that market. And one nice thing about that is if you’re tightly resource-constrained, then that experience can help you make wise use of that money by having a less feature-rich product; a simpler product. Maybe instead of having this medium-scope project, you say, “I’m going to do something that we can do in the next eight weeks.” Get that out there; start selling it; see what happens; get some experience. And that’s a call you’ve got to make. You know, we have clients that are going to go for the big score; and that’s what they need to be doing. They’ve got their resources; they’ve got the people; they’ve got the time; they’ve got the talent; and they’ve got the motivation. And we just help them do that. And we have other clients that are much, much better off coming at it from much more of a cottage industry approach. And so, in this case, they’re going to put less capital out and they’re going to sell less. And you know the upside – and maybe two orders of magnitude smaller – but at the same time, they’re not risking other things to do it.
And so that’s kind of where you have to decide is that, you know, what are you going to do? You just got to man up and go. And, I think the trick there is there’s some things to consider. And this is kind of the podcast from a little while back. Where, you know, do you have the funds to do it? Do you have the time? Do you have the energy? Do you have the motivation? Do you have the people? And do you have the people that are in the right spot? And so, there again, this is why all products live or die by the management team. Because that’s where you can make good decisions or bad decisions that, you know . . . if you’re not careful, you’ll make a decision that means you have a product that requires so much effort, it takes you so long to get there, that then there’s a risk you’ll never get there. I would say that with product development, generally, the longer it spreads out, the less likely it is you’ll ever get there. Now, there are exceptions to that, but for the most part that’s true.
So, I hope that you can take something away from this. And, look at it from the standpoint of right-sizing that product for your capabilities, your resources. And there’s nothing to say that if you do a simple product, you can’t come back with a complex product. So, just kind of decide. Think it through.
We’re happy to help you all the way through. Big. Small. Little. Massive. Disruptive. Incremental. We’re the engine that helps you push. And we get in, we help you push and we help you take it from that concept to the shipping dock. And we fill in the holes that you need along the way to get you there. Sometimes they’re small gaps; sometimes they’re big gaps. But, our job is to get in there and push.
I hope this helps out. If you have any questions, please don’t hesitate to give me a call, shoot me an email, visit our website. It’s 1-800-722-7987 – or – 919-481-1845. montie (M-O-N-T-I-E)@montie(M-O-N-T-I-E) .com is my email. Or just visit our website – www. montie.com. Thanks. Hope you have a great day. Bye-bye.
Audio File: 2014 Feb 25 – Design Process Steps Funnel.mp3
Audio Length: 12:01 minutes
Good Morning. My name is Montie Roland with Montie Design in Morrisville, North Carolina. I’m also with Montie Gear in Morrisville, North Carolina, as well.
Montie Design is a full-service product development firm. We provide everything from taking your concept all the way to a fully designed, fully engineered, ready-to-manufacture product, and helping you get that on the shipping dock. We can provide a value from the engineering side, from the industrial design side, to the project management aspect, and also from product validation, all the way to introducing you to contract manufacturers, and as-needed service liaison between your organization and the contract manufacture to make sure that it’s a win-win for everybody.
The design process has several steps. Those steps are intended to create a funnel. That funnel helps you to minimize the cost of the design process by starting out with a lot of ideas and a lot of concepts and boiling them down to the concept that is going to be the winner in the marketplace.
So, the next question becomes, well, how do you do that? So, if you use the funnel metaphor, with the funnel you’ve got a wide top. Let’s say you’re putting oil in your car. So you’ve got oil coming out of a jug, which is similar to the thought of ideas coming out of your staff, your constituents, your customers, and your stakeholders. And so, you pour that oil into that funnel, and the idea behind the funnel is you’ve got a big target. So all the oil you pour in starts running down the funnel. Well, the same thing; what we want to do is capture those great ideas, capture those concepts – written, verbal, unstated – capture those rules, because you know the design of your product has a lot of rules. And that’s because you’re in a market space where you have experience. So, as you put that experience to use, those rules have value because you don’t want to repeat any missteps in the past and you want to build on successes in the past.
So, what we do is the first step is to do research. There again, the research is akin to putting a second jug of oil in there. So we want to do research, understand what the market’s about. And then also make sure that we’re completely oriented to your market, and hopefully do a lot of the nuances of your market – some of that we have to rely on you; others, we can look at trends and research. So, that design research is the first step. And then the second step is to start pulling out concepts, thoughts, what we call “space shuttle ideas”, and do some ideation. And the initial ideation gets kind of everybody thinking, but I don’t want to pin any super solid concepts down yet; just get everybody thinking. And then what we want to do is do some brainstorming. So, now we’ve done some research, made a few sketches, enough to throw some stuff up on the wall and chew on it. And then we use brainstorming. And brainstorming is where there’s no such thing as a bad idea. Most people use a brainstorming session as a planning session; and it’s not. It’s a good way to ruin your brainstorming. Because some of the crazy ideas don’t work exactly as stated, but may lead to some really solid innovations. So, we brainstorm. Take that brainstorming results and then start doing ideation. Now, one of the steps that I just blew right by here as I was talking is we also want to create a style board. And we do want to do that in the beginning. That’s so that we can understand what you’re thinking. And a style board is to get your thoughts. With a style board, you bring us images, pictures, magazine clippings, polaroids; what have you. And show us things that you like. And, also, concepts that may be difficult for everybody to convey that doesn’t do this for a living, or just may be difficult to convey or it’s just a lot quicker with a photograph. For example, you may see a device on a piece of machinery. Take a picture, bring it to us, and say, I like how this device works; this could work great in our application. Or, I like the color; I like the shape; it could be the rear end of the Audi TT. Wow, these proportions are nice. So, we take that style board and we use that in our ideation. And we’ll also probably create one of our own. So, the brainstorming and the style board are very valuable tools.
Now, for some products, we need to do a personalities and personas session, where, kind of like a style board, we want to dig out a vision. So, with personalities and personas, we’ll design a product for an individual customer, and then we’ll go on to do this for a suite of customers that are very different – demographically, what they’re looking for, what they earn, who they are. You know, in some cases with some products we’ll throw in race and religion because there may be a cultural influence that we want to capture in our product development. And, yes, it’s important that you don’t design products for vanilla people, because vanilla people just don’t exist. So, what we have to do is look at the culture where our product’s going to be sold. If it’s a worldwide product, then we have to look at multiple cultures. What we don’t want to do is to create a product that won’t sell well in a given country because we’ve violated some cultural norm, and that’s really important.
So, then, we’re making sketches. We take those sketches and we review them. And it’s important to spend a lot of time looking and thinking about those initial sketches, because this is the inexpensive part of the project, relatively. Sketches are quick. So then we take those; we narrow a whole wall full of sketches down to a few concepts; work on those concepts. And the whole time we’ve been creating this design buffet. So what we want to do is create all of these concepts and all of these pieces, and then we can pick and choose from those pieces and some of those may integrate well together in the final product. So, there again, we’re starting out with a lot of ideas and then we’re narrowing it down as we go. So now we’ve got sketches of a bunch of ideas; we’ve narrowed that down to, say, one, two or three; and then we take those and refine those. And then we do a review again. Then narrow that down. So, the whole time, everybody’s getting a chance to provide input. If possible, we want to create a massing model. A massing model is a simple prototype that just reflects size and shape – simple, inexpensive, quick, you know, blue foam type prototype. Not something you show to the CEO unless he’s really hands-on. But something you can pass around between the product manager and the engineers and just in a, kind of, a closed circle of review.
And then we take that and narrow it down to one concept. Take that one concept and refine that concept. Get it signed-off. So, everybody needs to sign off, all the stakeholders, that this is the concept we want to move forward with. We take that concept and we go to the engineering stage. In the engineering stage we work out the nuts, the bolts, where everything goes. It’s important during the engineering stage to maintain the vision so that the engineers don’t lose track of what’s the aesthetic vision, what are the values, the, you know, it’s not just a collection of specs and bolts and nuts; it’s a product for a living, breathing people.
Somewhere in that stage we want to build a prototype. We want to build prototypes as soon as possible and as often as possible. So, once we have an industrial design concept and we’re starting to commit this to a solid model, a lot of times its good to build a cruder prototype, but one that’s actual size that may have some of the functionality as we’re going through the engineering process. At the end of the engineering process we want to build a functional prototype; maybe even an alpha unit. We’ve made drawings; we’ve gone out for quotes, created a bill of materials. As early in the process we want to start our bill of materials so that we’re starting to get an idea of what this is going to cost in production. From there, we transition to manufacturing. Make those introductions – Who’s going to make your product? Are you going to assemble it yourself? Is it going to come in a box, ready to go, from a contract manufacturer? We got to think about packaging. We may need to design you some packaging. Got to think about – Is it shipped over the Internet? Or is this a point-of-sale type product, where we need to have point-of-sale packaging?
And so we work through these issues and these challenges and opportunities, and create for you this product. And those are, in a nutshell, the basic steps. If you’re a Fortune 100 company, or an entrepreneur that’s selling your second product, you’re going to follow the same steps – maybe not as formally, but in general – you’re going to follow those same steps. As you can imagine, a change on a sketch early on is inexpensive; a change after you’ve fully engineered the product gets more expensive; and a change after you’ve started producing it is painful. So, what we want to do is pull out that vision; we want to get the stakeholders to weigh in, make sure that important parts of the product and those aspects are fully realized; and we don’t trip over something. Like, for example, an unknown requirement. So, by going through these steps, we minimize the risk of that unknown requirement popping up. And that’s one of the reasons you want to prototype early because usually when you lay something on the table, some of those unstated, understated or just not known products requirements start coming out.
So I hope this has been helpful. If you have any questions, don’t hesitate to give me a call – 1-800-722-7987. It’s Montie Roland. Or, montie (M-O-N-T-I-E)@montie(M-O-N-T-I-E).com. Or www.montie (M-O-N-T-I-E) .com is our website.
I hope you have a great day. I hope this is beneficial. Montie Roland, signing off.
Montie Design was founded in 2006 by Montie Roland (pdf resume, word, html), a practicing engineer looking for an outlet for his desire to design and engineer great products. Montie Design moved to Morrisville, NC in 2007 to add additional space and locate closer to customers in the Research Triangle area.
As Montie Design has grown, we have been fortunate to work on a variety of awesome projects in diverse markets from electronics to sporting goods. One quarter we’re designing rackmount equipment to go in data center. Another project, we find ourselves designing an environmental test chamber for Aberdeen Proving Grounds to test equipment before it goes out to the warfighter. We’ve created consumer products like the Invisi-ball and the Fog Thief. This type of variety is great because no two projects are ever the same.
Look to us for help with:
Mechanical Engineering / Product Engineering / Product Development
Electrical Engineering / Firmware / PCB Layout
Consultation on Product Viability
Product / Brand Management
Our President has this crazy passion for designing equipment to make life in the outdoors more fun and more comfortable. This passion was put in motion in 2009 when we started the Montie Gear product line. This was originally started as our own skunkworks for fun. In 3-1/2 years it went from a few concepts to a six figure a year operation. Today Montie Gear is a separate company and has over 30 unique products. While we are very passionate about designing products for camping, shooting and the great outdoors, we stand ready to put that same enthusiasm and knowledge to work designing and engineering great products for you. If you are looking for a shooting rest or slingshot, please www.montiegear.com.
There are several areas where we really stand out with the services that we provide.
Designing and Engineer Low-to-Medium Volume Products
Montie Design excels in the difficult area of designing low and medium volume products. We are experts at balancing capital / tooling expenses with product costs. With decades of experience in product engineering, we are ready to deploy our process and move your product from concept to market.
Electronics Enclosures and CFD / Thermal Analysis
The design phase is critical to keep electronics cool, avoid EMI / EMC issues, and predict thermal issues. We perform thermal analysis in-house using state of the art CFD (computation fluid dynamics) tools for accurate and reliable results.
We enjoy building rugged equipment for outdoor sporting and downrange applications with experience in shooting sports such as firearm accessories and slingshots. Camping, hiking, shooting and backpacking are passions of ours. We pour that passion into your product! This includes designing accessories for firearms, military, tactical and slingshots.
Gathering Social Reviews for Clients
We connect your new product to active bloggers, writers, and lead users to allow those experts to lend their credibility to your product. This is vital, because most customers now check internet reviews before purchasing. We can assist you in creating this base of reviews that are so critical for customers.
Strong Vendor Network
Take the risk out of receiving your prototype on time! Our great vendors, that we have successfully worked with for years, allow us to extend great service. Our responsive vendors provide a range of services that include waterjet cutting, rapid machining, rapid sheetmetal, paint, powder coat, rapid prototyping, rapid tooling and CNC machining. If we can’t do in-house, we generally have a local vendor that can respond quickly and help us make your prototype, or limited production run, a reality.
Sustainability Analysis Tools
Our easy-to-understand report shows your customers exactly where you stand when it comes to sustainability. There are no difficult to understand metrics. Our common sense approach will update your customers on the success of your product sustainability.
Read more at http://www.montie.com/#U6K8ukfuzCG59KDV.99
Audio File: 2014 Feb 17 – About Montie Design.mp3
Audio Length: 11:08 minutes
Hello, my name is Montie Roland. I’m the president of Montie Design in Morrisville, North Carolina. I wanted to take a few minutes to introduce you to Montie Design.
Montie Design is what we call a full-service design firm. We provide mechanical engineering, industrial design, and we also build prototypes. There are also requirements that we need to fulfill for electrical engineering and software development and firmware development. And so we can help with that as well.
Our core competency is those first three – mechanical engineering, industrial design and prototyping. What we do is fill in gaps. We take your project and we go from an estimate to a completed job. Usually a kind of a workflow, when it comes to a project, goes through several stages. The first stage is the information gathering and understanding. Well, what we want to do is understand what you need us to accomplish so that we can put together a proposal. And that proposal is usually an estimate with stages to it. Sometimes we work against an estimate on a time-of-materials basis, and other times we work as a firm fixed price.
Projects go from, you know, creating that estimate to . . . the next stage is usually the industrial design stage. The industrial design stage is where we sit down, work with you to understand your vision. And then take that vision and commit it to concepts on paper. Sometimes those are hand drawn sketches; sometimes those are computer generated assets. But what we want to do is take your vision and pluck that vision out and then get it down on paper so we understand it. Then we also want to take our understanding of other industries and see where we can bring other techniques, other technologies and other approaches to bear. So what we’re trying to do there is to make sure that your product has the benefit of the knowledge that we’ve gained over the years doing projects for other people.
And that way you’ve got a broad perspective on your next product. We want to look and see what, you know, what are people doing in your industry and what are people doing across other industries. Bring that into the product development process so that your product is robust, fits the market, and also, you know, we’ve looked to see where we can bring value to your product and to your customer by bringing in other technologies and other approaches and other thoughts.
So, we take that; generate sketches and additional assets, depending on the project. And then we may build what’s called a “massing model”. And a massing model’s a prototype where it’s really only meant to show size and shape and just general, is it the right size. So, you can hold it. It’s usually not functional, but it gives you a feeling; you can actually put it in your hands, turn it, show it to people. A lot of times what that also does between that and the sketches and the renderings, compare that to your spec or, if need be, we can develop that spec for you. And once you put something down on the table, that’s also when the unwritten requirements come out. Because that’s when someone says, “Hey, Montie. We need to do this” or “No, this can’t be more than two inches tall” or twelve inches or one-six pounds or it needs to do that. And those undocumented requirements are understated requirements then have this opportunity to flow out; we can capture those early on because finding out that the product didn’t perform as advertised at the end of the project is not good. So, we want to capture that in the beginning so we build in success from the front.
We go from there to an engineering phase. As soon as we can we want to build a prototype. In the engineering phase we take our mechanical engineers, start making solid works, solid models. Testing those models with computer-aided tools like finite element analysis or computational fluid dynamics (or CFD) for airflow and thermal analysis. We use that to, I guess, prototype digitally and then pretty quickly we want to build a mock-up. And depending on the project and the scope, some mock-ups may be to test a particular thing; for example, airflow. We might build a mock-up that’s aimed completely at testing airflow to verify and validate our CFD results.
So, then we go through there and build models in the computer (SolidWorks). And then build a prototype. And as we go forward our prototypes, you know, the cost of these prototypes increases. Obviously, if you’ve got a block of foam that someone worked on for an hour its much less expensive than if you have, you know, a fully functional, fully developed engineering-grade prototype that tests out functionality, aesthetics, manufacturing concepts. So we want to match the prototype to your needs, or the needs at that point. There again, so we want to make sure that we’re containing costs where we need to. And make sure that we’re providing you with high value for the money you’re spending.
So, build a prototype. Test that prototype. Make any adjustments to the design based on that testing. And then go out for quotes. So we go out for quotes and come back with a costed bill of material. So you now know what it’s going to cost to build your product and production.
So, we’ve added some tremendous value in several areas here. One is that we’re helping you to leverage our relationship with vendors and component manufactures, contract manufacturers. So we’re taking our relationships, introducing you to the people you need to be introduced to. And then also working with them to generate this costed bill of materials that tells you what it’s really going to cost to manufacture your product at the quantities you want to sell it at. And that’s something we’re good at. That’s something we bring a tremendous amount of value to the table with. Because of those relationships, because of our understanding of how to make this happen, and also, too, to help save you money because you’ve got folks that are on your side (us) and helping you work through questions with vendors and contractors. And so we’re putting our experience to use. And also, you may have all this experience in-house. At the same time, it may be what we’re simply doing is providing a relief for your staff, so they can be doing other potentially higher-value activities, or things that they’re better at, and then we can work on the things we’re good at and get those through your pipeline quicker, and to where they’re on the shipping dock and you’re selling them and you’re adding to your bottom line.
So, at the end of the day, our job is to help you drive towards improving your bottom line. We want to have products that are robust and that are profitable and that are manufacturable. That’s Montie Design. We take you through that process. Our job is to serve you and help you turn that next product concept into that next product winner.
If you have any questions, please don’t hesitate to give me a call – it’s Montie Roland, 1-800-722-7987. Visit us on the web – www. montie.com. Or shoot me an email – montie (M-O-N-T-I-E)@montie(M-O-N-T-I-E) .com. And my staff, as I say, we’re here to serve you; do a good job for you, and add a tremendous amount of value to your product development and engineering process. Please give me a call and let’s talk about that project that’s on your desk, or the one that’s going to be on your desk soon, and let’s make your life a little easier and your company more profitable. Montie Roland, signing off.
Audio File: 2014 Feb 12 – Developing A Product.mp3
Audio Length: 8:07 minutes
Hello. My name is Montie Roland. I’m with Montie Design in Morrisville, North Carolina.
Whenever you undertake the development of a new product, there’s a series of decisions that go into that product at a very early stage. One of the things that’s very, very important to do is to validate that you should build the product. Because if you build a product that won’t sell, then you’ve tied up resources in something that will never generate a return on investment. So one of the things that I think is very, very important is to develop a skill set of saying, Okay, here’s why I think this product will sell; being able to work through a process of helping you get to that validation. And then being able to take the results of that validation and make a go or no-go decision. This really applies to all practitioners, be it corporate in a monster company, a medium-sized company, or an entrepreneur or inventor.
So, let’s start out with a case of being an inventor. Or, actually, I take that back. Let’s look at it from a hundred thousand foot view. So, some of the things that have to happen before you can sell your product – one is that you’ve got to have the money to develop it; you’ve got to have the money to manufacture the first run; and then you’ve got to have the money to market it. Many times – individuals especially; entrepreneurs or what have you – will say I’ll find the money; let me develop the product first. Well, in a way they’re getting the cart before the horse for a couple of reasons. One is that you want to make sure that your development of products that someone will help you fund (if you’re looking for that kind of thing; you’re looking for external funding), and then the other is that you want to make sure that you’ve thought through these first stages. So, things that need to be considered, or issues that need to be considered: One is what’s the development cost? And can you afford the development cost? Two, what does it cost to manufacture the products? Can you afford that first run of products? Three, what does it cost to market the product? And do you have everything in place that you need to do this? Now, in a big corporation this is broken down into segments, generally. So, there’s a group within the corporation that handles marketing. There’s a group that handles sales. A lot of product specifications are determined by the sales group, because they see a hole in the market, or they have requests from clients that want Product A. So, in a larger corporation you’ll have a multi-service team that will look at this from two directions – look at it from an accounting standpoint or a financial standpoint, a business standpoint, an engineering standpoint. And so go through those motions before the product is actually kicked off, just to make sure it’s the right product and they’ve got a way to pay for it.
Other organizations that are smaller may skip parts of this process. Entrepreneurs are notorious for doing this, because the fun part is designing the product; the fun part is usually not figuring out how to pay for it. So a lot of times entrepreneurs will put a lot of work into a product because they think it will succeed based on not a lot of research, and then they’ll get to the end of the product development cycle and either have developed the wrong product (which won’t sell), or they’ve just developed a product that won’t sell; or, because they’re out of resources, now all of a sudden, they can’t go any farther. We see a lot of the latter. That’s pretty common. So there’s a lot of great products that sit on the shelf and die.
So before you undertake that project, I would say consider – Do you have the money for each step of the way? And really you need to have the money for enough to keep you going through the ramp up of the adoption curve. And the adoption curve is how quickly people pick up a product or buy a product after its released; how long does it take the market to respond to that product. And that adoption curve is definitely there. It’s exponential, so it’s flat at the bottom when you’re first starting out; and then at some point we all hope it goes exponential vertically.
And then the next question is do you have the resources to pull it off – Do you have the engineering resources? Can you afford to buy them if you don’t? Do you have the management resources? Do you have the facilities resources? Most companies fail because of the management, not because of the product. Most product given companies do.
So I think its important to lay these things out, make a decision about them, whether or not you have them; make a decision about, you know, is it the right product; is it the right market; is this a difficult market. And that way you’ve made these decisions upfront before you’ve committed a lot of time and money to something that you may realize later on wasn’t such a good idea. So by doing this you’ll actually save yourself effort in the long run; you’ll be better prepared to design your product; and there’ll be less risk as part of the process.
If you have any thoughts or comments about my comments or thoughts, please don’t hesitate to give me a call – 1-800-722-7987. Shoot me an email – Montie (M-O-N-T-I-E ) @ Montie dot com. Or, visit us – www.montie.com. Thanks and have a great day.
Are you a maker? Who are makers? Lets spend a few minutes and explore this amazing and sometimes wacky world. Keep in mind that the makers are influencing how you do business and that influence is rapidly growing. According to Wikipedia:
The maker culture is a contemporary culture or subculture representing a technology-based extension of DIY culture. Typical interests enjoyed by the maker culture include engineering-oriented pursuits such as electronics, robotics, 3-D printing, and the use of CNC tools, as well as more traditional activities such as metalworking, woodworking, and traditional arts and crafts. The subculture stresses new and unique applications of technologies, and encourages invention and prototyping. There is a strong focus on using and learning practical skills and applying them creatively.
Makers are people how build stuff. Some of these makers are just hobbyists and crafters who use technology to create their products. Other makers are entrepreneurs who use what is now common technology to build innovative products in their garage. It would probably surprise you how many individuals now have CNC machines or hobbyist grade 3d printers in their garages. Over past ten years several technologies and enabling products have had a huge impact on democratizing design. These enabling products and services include:
Designing any great product is easier when the designer and engineers to have an appreciation for how they are making the customer, reseller and distributor’s life easier and more profitable. This podcast explores how I was motivated to design products for the camping / glamping market. We’ll also explore what it means to have a robust product.
Call me at 800.722.7987 or email firstname.lastname@example.org or visit montie.com to discuss how we can help with the design, engineering and prototyping of your next product.
Here is the transcript from the podcast.
Hi, my name is Montie Roland. I’m with Montie Design in Morrisville, North Carolina.
I’d like to spend a few minutes today talking about keys to success in designing an outdoor product.
Let me tell you a little bit about what we do. Montie Design is a product development firm. And we’re also the manufacturers of MontieGear line, which is a line of outdoor and shooting-related products.
I personally enjoy designing products of all kinds. One of the products I enjoy the most is products that are outdoor related. I enjoy spending time in the outdoors – enjoy camping, enjoy backpacking – so I’m always trying to come up with, you know, what’s a way to make that trip more pleasurable, safer, easier. Or what’s a way to extend the capacity and do something better.
I think a lot of us have spent time camping. A lot of times, when we’re growing up, maybe going car camping . . . maybe you just went once or twice. Maybe it was with Indian Princesses or with Boy Scouts or Girl Scouts. But being outdoors, there’s a certain freedom and there’s a certain . . . lack of captivity then you are when you’re between four walls. Now the trade-off is that you got to work a little harder. It’s . . . not as comfortable, sometimes. You’re out of your comfort zone. You don’t have some of the comforts of home. And so . . . equipment over the past few years has changed in some ways; in some ways it’s very similar. When you’re camping, you want to be comfortable. You know, one of the horror stories you see on the commercials and on TV (and maybe experienced) is getting wet. You know . . . my daughters and I were camping in the Shenandoah’s a few years ago, and Hurricane Bob came through. We had no idea which way that hurricane was going to go. And we had planned this grip in advance and we finally said, Hey, let’s just go. And worst case? We’ll just drive home. And so we were up in the Shenandoah’s and . . . it rained. And . . . and then the tropical storm actually passed over. And it rained. And, did I mention it rained? Yeah. And in between the rain, there was rain. So, needless to say it was a challenging environment for about . . . I don’t know – twenty-four hours? When it rained for twenty-four hours. Did I mention the cooking in the rain? Or no . . . yeah.
But, anyway, so our tent wasn’t up to the challenge. Now, thankfully, our Aerobed was. So, late that evening, our tent in one corner had about two foot of water in it. And the average depth in the tent was probably six inches. Now, we were car camping, and thankfully, we had put everything in boxes, these waterproof . . . or, pseudo-waterproof boxes, because we had stuff in the truck. So, we had the bed full of camping gear. And . . . so when it rained and tent flooded, we . . . we were laying on the Aerobed, and the Aerobed was floating. Our boxes were floating. So, if you wanted something out of a box, you had to reach over and grab it, pull you to it, take the lid off without tipping it over and bringing water in. Also had to be real careful not to let your sleeping bag fall off the Aerobed, because if you did, it was wet.
So, it was definitely challenging in that way. I think that we still had a good time. Have to ask my daughters. I might be being optimistic. But . . . so in that case, the product didn’t live up to the challenge. I ended up taking the tent back.
So, when you’re outdoors, one of the things you want to provide with your products is you want to enhance the comfort of the trip, if you can. Now, the product may itself enhance the comfort. So, let’s say you’ve got an inflatable mattress, making sleeping more comfortable. That is so nice when you’re camping. But at the same time, I think it’s important to also think about how the product’s carried, how it’s stored, how it’s used. So, for example, you may enhance the comfort of the trip by making an existing product easier to carry. So, for example, if something’s big and bulky and takes up too much room in the car, or in your pack, then you may find that it’s really uncomfortable. Or, let’s say that for some reason it pokes you in the back in your backpack; when it’s in the backpack, its poking you in the back. Or it’s causing some sort of other transportation dilemma. So, how the product is carried, how it packs, how easy it is to pack – those are all things that can help make your trip more comfortable in that respect. And also, less work. One of the things with our Montie Gear products that we push is to have products that are very, very easy to assemble. Because when you’re tired, it’s raining, its dark, its cold, the last thing you want is to have a product that’s overly complex and difficult to assemble. Because once that happens, those conditions amplify the difficulty of using it, assembling it, breaking camp, what have you. And you’ve lowered the user’s perception of the product, possibly to the point they’re done with it.
So, you always want products that are easy to assemble, easy to use. Just because something’s that easy to assemble on your desk at work, when you’re sitting in a comfortable chair and not hungry, not tired, no rain, seventy-two degrees . . . you may be able to do it on your desk and go, Well, that’s not so bad. But then once you get outside, in the outside environment, looking for twelve pieces that you just dropped onto the ground and now found out that the color they are is perfectly camouflaged – those all add aggravation. So, you want to have products that are low aggravation. And generally, readying the product for use – assembly, what have you – is an area where we’ve seen a lot of . . . I have personally when I was camping seen a need to really think through the product. So, you want a product that’s comfortable; you want a product that easy to assemble, easy to bring to bear, easy to stand up. We want a product that is easy to use. There again, if you’re sitting by the fire and its dark, having some precision alignment of holes before you can put something in a pin, before you can, you know, use it; maybe you have to take it apart between uses and put it back together. Well, if it’s difficult to do in the dark, there again, you may have a product that just doesn’t fit that environment.
So, that . . . that goes to the issue of being robust. Robust products are easy to use, easy to assemble, and hard to damage. And give you . . . also, I will argue that a truly robust product gives you ways that you can use it in ways that the designer never intended. So, maybe there’s a “I intended to do ‘A’”; your customer does “B”. At that point, that’s a really valuable piece of feedback to know because that may open up a whole new market for you. Or, give you an idea of a new product you should design.
So, robust products are ones that they are just easy to use, hard to damage, and easy to assemble, easy to take down, and give you options. Sometimes you can do stuff twelve different ways. Sometimes it’s one, depending on the product.
So, the other thing is you want products that are rugged when you’re designing for the outdoors. Now, sometimes you have limits on that, how rugged they are. A great example is a tent pole. Tent poles, by nature, tend to be fragile to keep weight down, especially with backpacking tents. So there’s this implicating understood trade-off that when I lay out my tent poles from my backpacking tent on the ground, I don’t want anybody around because I don’t want anybody to step on it and bend it or break it. And so I understand that the trade-off of having a four-pound-ten-ounce tent is the fact that the poles are delicate until they’re assembled. Now, they’re easy to assemble with a shock-cord and so forth. But until they get into the tent, they . . . can be hard to . . . can be delicate. Now, once they’re on the tent, they need to be extremely robust. That fifty-mile-an-hour wind, or that six inches of snow, that tent needs to come through that, and that pole needs to do its job with no problems what so ever.
So, there are times when the rugged nature and the robust nature has to be within a specific pattern of use, or a specific part of a pattern of use. And I think the other thing that’s important when you’re camping is that you want a product that looks like it should be a product when you’re camping. Now, one of the things that has changed about this is that for a long time camping products were very functional. They looked like something that you’d buy at the Army Navy Store. A good example is Coleman stove. A white gas later gave way to propane. But, they’re great, they’re rugged; you can fix them with a . . . a knife and a screwdriver, some oil; and they’re just great products – they last forever. And I think long life is usually a by-product of having something that’s rugged and something that’s robust. So, a lot of these cots and other things just look like something the military would use. Now, what happened a few years ago is REI came on the scene, a great outdoor provisioning company. And all of a sudden, camping became more upscale. And so as these stores competed for dollars, one of the ways that they made themselves more distinctive was to provide very high quality, very robust products, and provide them at a higher cost, because higher quality robust, what have you . . . and that also gave the opportunity and the need for more industrial design. Where thinking through the customer experience, the customer experience behind the counter, or in front of the counter; customer experience in the field; what the customer sees on the website; reviews; what have you. So, the world kind of changed and now we have camping products that a lot of times are beautiful as well as tough.
And so, with a camping product, you got to also . . . you know, where does it fall? Is it an inexpensive product? And Coleman is an expert at providing relatively inexpensive, less frills, less performance products. Or, is it a product that is a higher quality product and a higher end product (something you might see at REI)? And then in the past few years, there’s also been a switch to what I’m going to call “Glamping” products. And I think glamping . . . which another way to look at it is called “glamorous camping”. It’s something we can thank the Europeans for. And we were headed there anyway. But, in Europe, you can go camping at a campground and camp in a two thousand square foot tent with flat screen TVs, satellite cable, Persian rugs, couches, that are really, basically, high-end homes made out of fabric. And so the option of doing glamping, I think, is starting to come to the U.S., and that’s going to impact some of the products that are designed for this market as well. So, just to keep that in mind, you’ve kind of got a low-to-midrange, which is the Coleman products; a lot of products that folks who own RVs buy; and then the mid-range . . . mid-low-or-high, which is REI – so you’ve got brands like Patagonia, you know; Merrill. And then you’ve got high end, the glamping products. And that kind of gives you, hopefully, gives you a framework of where to start when you have to look at how you’re going to structure this product. Where does it live? And, also, to evaluate whether or not you’ve got the right product designed. How effective it’ll be in the marketplace.
So, these are some criteria. Just to summarize. You want a product that’s rugged. You want a product that’s robust. You want a product that’s high quality. You want a product that fits the intended market segment, be it the lower end (the Coleman, a lot of the RV products), the mid-range (the REIs and Great Out Door Provision Company-type market); or the glamping market. You want a product that’s easy to use, easy to assemble. You want a product that’s easy to assemble when it’s almost dark and raining and cold. You know, can you assemble this product with gloves? Is this a product where once it’s . . . it’s hard to damage once it’s installed, but is easy to install. So, in camping, it’s a very tough market because it’s so functionally driven and so user experience driven. And then also, too, yeah, always keep in mind is that you’ve got different types of camping. You’ve got car camping. You’ve got glamping. And, of course, car camping being you drive your car to up to where you’re going to camp; you unload everything. So, weight and size isn’t so much of a penalty; comfort’s a high priority. Backpacking – weight is everything. Comfort – eh, not so much so. And ruggedness in backpacking is very important, but you have a more sophisticated user that understands that you don’t want to bend that tent pole when you’re twenty miles from anywhere.
So, keeping all those in mind, I hope you design some great outdoor products. If you have a product that you need . . . maybe you’ve got a concept and need us to design an product and then build a prototype and help you get it into manufacturing, or just some small part of that, give me a call, we’d love to help.
Montie Roland, Montie Design, 1-800-722-7987. Or montie (M-O-N-T-I-E)@montie(M-O-N-T-I-E).com. I hope you have a great day. I hope this podcast was beneficial for you. Montie Roland, signing off.
After many years of setting up projects for our industrial designers and mechanical engineers, here are my thoughts on some basic best practices on how to structure your files and keep your project organized. This segment examines a very useful tool for the engineering and product team: the costed BOM.
Here is the transcript of the podcast:
Good morning. My name is Montie Roland. I’m with Montie Design in Morrisville, North Carolina.
And this morning, what’d I’d like to talk about is how to structure your project from a file standpoint, from an organizational standpoint.
Montie Design is a full-service design firm in Morrisville, North Carolina. We provide industrial design, mechanical engineering and prototyping capability on-demand to help you move your project from concept to ready-for-the-shipping-dock.
So, we’ve talked about our Current Design, Released [directories]. . . let’s go back to Released for a second and talk about reving Assemblies or not to rev assemblies. It’s going to be driven by several things. One is if your design changed dramatically and the assembly doesn’t look like the parts, you need to rev the assembly. Other times you may need to rev the assembly is if you have a vendor that has a PLM system that is tied to the assembly rev. It doesn’t have the flexibility to control it without . . . to make a change to their drawing set without a revised assembly. We’ve seen that. We have a project right now we’re working on; they don’t have that control. So if we make changes we have to revise the assembly just because we revised a part. And the problem is that if you have to do that there may be a lot of subassemblies in-between; so it’s definitely a lot of work to do that.
And so you’re kind of starting to see, as a manager now, why sometimes your engineers are reticent to . . . to do revisions, because there is some work to it.
So other directories that you’ll need – one is that I create a “Project Management” directory. Project Management directory has contracts; has any schedules; things that you need in managing the project, but maybe not necessarily need to execute the design.
So another thing we would do is that we want to create a Bill of Materials. The Bill of Materials is sooooo handy. As the project goes along, you’re Bill of Materials is going to become a costed Bill of Materials. So at the end of the project, what we want to see is we want to see a . . . a Bill of Materials that has a part number, description, a revision, and has the costing information. Now, dependent on the project there may be some projects where that’s completed handled by the client. For a MontieGear project, one of the last steps is to make sure that Bill of Materials is correct, has the costing information, and then . . . that is used by the person doing the pricing, which often is me for MontieGear. I will take that, and if that Bill of Materials is done correctly, what I can then do is add the cost of labor to do assembly; any shipping costs; and then I know how to price the product without going through and pulling up a bunch of drawings. And this is so important later on. It saves tremendous amount of time.
So, as you go through the project, other directories you’re going to want to have is “Quotes”. So, every time a quote comes in, scan it in; if it’s electronic, save it. Create a directory of Quotes from your vendors in one spot. So, that’s a subdirectory under your Project directory. You’ve got Quotes. So, we’ve done Current Design, Concepts, Quotes. Another one you’ll often have is something called “Files from Client”. And so those are files that the client has provided. These are documentation that where they’ve given you pre-project documentation; there may be initial version of a product specification. And so this is that repository of those documents. Then again, a lot of times we’ll save those file names by date; if it’s a quote we’ll save it by date and vendor name and then possibly, you know, what that is if it’s a single pat quote. So you can quickly scan down that directory and find the quote for the lower left beam, or what have you.
And you may have other directories as needed. Those will depend with projects. One of the other things we do is create an images directory. And then the Images directory, underneath it, we’ll have a description of generally what that image is about. So, it might be /images/first prototype or date-first prototype. Date . . . Proof of Concept; Date-Alpha Prototype; Date-Beta Prototype; Date-Installation. So, that way you can scroll through there and quickly find those images. It’s also a great place if you’re . . . if you’re a manufacturer to also put your . . . your product shots, or your products-in-use. Maybe they’re static images done in the light tent. But that way you’ve got a great way to . . . to go find that because it’s tied to the project.
So this Project directly, theoretically, if you were to just copy that to a flash drive, it would have everything you need to continue with that project. And that’s good because over time hard drives change, files get deleted, directories get changed. So if you encapsulate everything in that subdirectory, then that makes life a lot easier.
So, kind of to roll back through this, we’ve got parametric files and we’ve got non-parametric files. And then we’ve got files that are often edited. And so, the parametric files are Solid Works files that could be inventor; it could be Pro-E. But those are files that need to be kept together; need to be moved using a Pack and Go. And occasionally with your current design, one way to make sure you’ve got the correct files in there is to Pack and Go to a temporary directory; delete the files in Current Design; and then copy those back in. And that way you know you don’t have some superfluous files in there.
Other files that we’ll create and need to do something with are . . . are non-parametric files. So, these could be IGES, STEP, DXF, DWG. And these files, in the Release directory, it will have the parametric files, plus a PDF of each drawing and maybe a DXF or DWG, if that’s needed to do a cutting process, a 2-D cutting process, like water jet, or sometimes a machine shop if they’re working from a 2-D file.
Also have the 3-D non-parametric files, like STEP or IGES. And so that way, in that Release directory, you’ve got the CAD files, plus you’ve the file you’re going to send out to vendors, the non-parametric files. And probably this would be a good spot for your Bill of Materials for that Rev. And so, in this case, a lot of these files follow the same format. Its part number . . . for us, at least, its “part number – description_rev “ and then the two-digit revision code. So, 00 or 02. And so we do this to keep these file names consistent so they’re easy to read through quickly. And that way everything is . . . you get to . . . you can very quickly figure out what you’re looking for. If you don’t maintain control over file names, you end up with file names that mean something to one person today, but may mean nothing to someone later. And, six months’ from now, may not mean anything to the person who named it then. So, I think it’s very important to maintain that . . . that control; have a strict doctrine over that.
That Bill of Materials? It’s important for costing purposes if you’re a manufacturer, because that way you’re engineer is taking what they’ve learned when they went out for quotes, or the purchasing agents wouldn’t . . . so, whoever went out for those quotes enters that into your Bill of Material, so now you can do your pricing quickly without having to go look for a bunch of information which may be harder to find.
Also, storing those quotes is valuable because then that . . . because then you’ve got a way to address that quickly, there again, without having to go look through emails or . . . look wherever [other places on the server].
So, from a hundred thousand foot view, what we want to do is we want this project directly . . . directory to provide everything you need to pick up that project, modify that project, price that product, or deliver to a client. And if you can do that then that helps multiple phases of the organization; not just engineering or industrial design, but also purchasing; it’s great for a reference later, for sales and marketing, because they understand what’s driving the cost; and it’s just a win-win all the way around. And that . . . that’s important to main . . . there again, to maintain that discipline because it’s not only helping you in the engineering stage; like I said, you’ll reap benefits for . . . the life of the product, especially if you ever have to go back and make a change or you ever have to go back and re-price or pricing on components change. It’s a great tool. And having that in a standard format is . . . it just benefits you.
If you have any questions about this, please don’t hesitate to give me a call. I know it’s kind of a long section here and technical, but happy to entertain your calls, questions. It’s 1-800-722-7987. That’s Montie Roland. Email – montie (M-O-N-T-I-E)@montie(M-O-N-T-I-E).com. Or you can visit our website – www.montie.com. You can see the results of client work we’ve done at the montie.com website. Or you can see some of our projects that we’ve done for ourselves at montiegear (M-O-N-T-I-E-G-E-A-R).com.
I hope this has been beneficial. Montie Roland, signing out.
After many years of setting up projects for our industrial designers and mechanical engineers, here are my thoughts on some basic best practices on how to structure your files and keep your project organized. We’ll concentrate on the importance of Pack-and-Go’s in this segment. This is a very important set of practices that will help keep you out of trouble. These concepts are important even if you have a PLM system, because it helps you understand how the PLM helps keep you organized.
Here is the transcript:
Good morning. My name is Montie Roland. I’m with Montie Design in Morrisville, North Carolina.
And this morning what’d I’d like to talk about is how to structure your project from a file standpoint, from an organizational standpoint.
Montie Design is a full-service design firm in Morrisville, North Carolina. We provide industrial design, mechanical engineering and prototyping capability on-demand to help you move your project from concept to ready-for-the-shipping-dock.
The Concept directories are where you’ll store your sketches, your ideations, maybe your solid model concepts, pictures for your style board. So then, when you think about these files we’re starting to store, you really have two types of files. One type of file is parametric, and the other type of file is static. And then really . . . I guess a third file would be like a . . . a file that’s directly editable. When it comes to Cat files, though, we have two types.
So, parametric files are files that are linked or potentially linked to other files. This is very, very important to keep in mind. So, with Solid Works, we can save a non-parametric file to a format like STEP or DXF or IGES or DWG or PDF. These non-parametric files can be edited, like, easily in the case of DXF or DWG; less easily in the case of PDF. And so these files, though, are generally not going to change just because you changed something somewhere else in the Solid Works model. However, the Solid Works files from Solid Works are parametrically linked in many cases. So, for example, a drawing file is going to go reference the part file to rebuild the drawing. So, if the part file is missing, it can’t reference it and can’t rebuild drawing and get a, basically, a blank screen in the middle of your . . . your drawing. So this is very, very important to keep in mind. Whenever you move files from one directory to the other (and occasionally you need to do this anyway), you run the risk of orphaning a file that’s somewhere else. So a good example of this is . . . let’s say I’m working on (in Solid Works) and I got to McMaster Car and I download a screw (which is a great way to get a screw). So, I download that screw and then I open it up; it comes across as a STEP or an IGES, and then I import it into my model. And when I hit “save” that McMaster Car Screw was saved to my download directory on my local machine. So, if I don’t consciously save that to my Current Design file . . . Current Design directory on the server, then . . . or on the Z-drive, then what’s going to happen is that now I have files in two different places. So, if I was to go and grab Current Design and move it into Release, let’s say. Just copy it over. I would leave that screw behind. Because the copy tool in Windows Explorer does not know about the relationships in Solid Works. So, it doesn’t know to go grab that.
Solid Works has this wonderful utility called “Pack and Go”. Pack and Go finds every file that’s linked to the files that you have open. So, what you want to do is go to the top level of, let’s say, Drawing. Or top-level Assembly. Open up Pack and Go, and then it’ll give you some options. And, generally, you want to exercise all those options in terms of including drawings, including . . . textures, including decals, FEA results; grabbing all that’s good – that way you don’t leave something behind. Solid Works will go look for those files, make a list of them, let you see that list, and then you pick a location where you either want to save that as a zip file, or you want to save that . . . just to that directory; drop the files in that directory. So, you choose that directory and then you hit “Okay”. Then Solid Works will think, and then it will start grabbing files and copying them to that directory. If you do not do this, it will bite you. It is not a question of if it will bite, it’s a question of what moment, what day, and how bad. Because we’ve seen this before. You can imagine that if you have files on a local machine and you just copy them over, or you copy them between places on the Z-drive or what have you, and you orphan some of these files, it can be very painful to find those, get those back. And then you’re never really sure you have the right one. So, let’s say you orphan a single screw. Okay. Worse case, you go download it from McMaster again. But let’s say that you have somehow ended up with a part file that’s in an unknown Rev (or even if we know what the Rev should be) and maybe it’s in some directory. It can very easily happen that you inadvertently saved it to the wrong directory. So, maybe you’re working in Current Design but you’re using a file from Rev 02. But that file is actually Rev 07. So, you grab the stuff out of Current Design, move it to Rev 08. You missed the Rev 07 file. Well, now, all of a sudden, we’ve got no clue where to find that file. And it’s difficult to find without pulling up every single file in . . . on the . . . in the subdirectory on the Z-drive and on your machine, and try to figure out which one it is. And even then, we’ve got to go by the Revision number and properties. And that’s just painful because that still doesn’t tell us it’s the right one. Because there could be, like, a 7 there and an 07 here and which one’s the correct one.
If you do Pack and Go, you avoid soooooo much of that trouble. It’s . . . Pack and Go is your friend. I just . . . this is one of those things that’s important to emphasize.
So, a similar thing applies to other programs. For example, PowerPoint has a Pack and Go feature; use it. Grab all of these images, put them in a Pack and Go file, because that . . . most of the time when you’re working on projects, you end up with images in different subdirectories. It’s on a local machine. It’s on a . . . it’s on your network. But if you do Pack and Go it grabs all those and puts them in the same space. Yes, you use more disk space. I’ll argue that disk space is dirt cheap compared to a few hours of looking for a file you can’t find ten minutes before your deadline.
The same goes for . . . you know, you’re working in an Adobe product. If you have the option to embed it in the file rather than link to it – embed it in the file. I realize this can make your . . . catalog a gigabyte in size. But, it’s so much better than two months’ later pulling it up and missing files. There again, disk space is cheap; time’s not. So, embed those files. Pack and Go. You know, use these features in these programs so that it makes it easier.
Alright, so, it’s also important to note that you have a PLM system, and you do check-ins and check-outs. It’s going to be a little different because that software is going to manage a lot of what we’re talking about. So, I’m not . . . I not sure. I think it’s beyond the scope of this podcast to go in depth on . . . on the PLM systems. But, they’re great. They’re awesome. They help manage some of those. So, in this case, we’re just talking about the manual.
But, on the other hand, if you understand the manual, it makes it a lot easier to understand the PLM.
If you have any questions about this, please don’t hesitate to give me a call. I know it’s kind of a long section here and technical, but happy to entertain your calls, questions. It’s 1-800-722-7987. That’s Montie Roland. Email – montie (M-O-N-T-I-E)@montie(M-O-N-T-I-E).com. Or you can visit our website – www.montie.com. You can see the results of client work we’ve done at the montie.com website. Or you can see some of our projects that we’ve done for ourselves at montiegear (M-O-N-T-I-E-G-E-A-R).com.
I hope this has been beneficial. Montie Roland, signing out.
After many years of setting up projects for our industrial designers and mechanical engineers, here are my thoughts on some basic best practices on how to structure your files and keep your project organized.
Here is the transcript:
Good morning. My name is Montie Roland. I’m with Montie Design in Morrisville, North Carolina.
And this morning what I’d like to talk about is how to structure your project from a file standpoint, from an organizational standpoint.
Montie Design is a full-service design firm in Morrisville, North Carolina. We provide industrial design, mechanical engineering and prototyping capability on demand to help you move your project from concept to ready-for-the-shipping-dock.
It’s always good to have processes and procedures. Now, I think . . . and, of course, any company can take that too far. And the counterpoint is if you take it too far, then you get that big company mentality and you’re painful to deal with. But, a lot of these processes and procedures benefit the company. I’ll be the first to admit that, as we’ve grown, we’ve . . . I’ve not been the biggest proponent of procedure and process, because, as a small group, you get everybody reading your mind and you don’t have to worry about it. But . . . this changes as you have more employees, because you have different levels, different capabilities, you have to keep re-training. And so, all of a sudden, it’s more important to have policies and procedures just to make life easier for your staff.
It’s also important when you think about interns. You’ve got someone’s who’s going to be there for a limited amount of time. You want to get them in, get them trained, and get them some experience; and then also get some work product completed so it’s a win-win for both the employer and for the intern.
So, let’s just dive in. A lot of these topics I’ve covered in past podcasts were much more . . . higher level. And so, this case, though, I want to dive in and let’s talk about this in detail.
So, first thing is that when you think about how do you organize your files. You want to have a place that everybody can get to. So, let’s say . . . let’s call it the “Z-drive”. And on the Z-drive, you have a space that is a shared working space. Now, what you need is you need a set of rules so everybody knows what to do. On a project where there’s more than one contributor, you really want to have a gatekeeper. So, the gatekeeper is in charge of files that go in certain locations. One is that files that go in current design and the other is files that go in your release directories. So, let’s kind of roll through those directories so I don’t get too far ahead of myself.
So, we’ve got a project direction. Let’s say our project is Zigsess (spell that one). And so, we got the . . . so I created a directory in this case . . . maybe for the client Zigsess. And then I have to make a decision. Is it likely I’m going to have multiple projects from this client? Or is it likely that I might just have . . . one. Or, not now . . . So maybe what I’ll do . . . I’m thinking that this might be a repeat client. So, let’s say that, if it is, then I’m going to want to have a directory for each project that we do for that client. So, we’ve got a directory called “Clients”; and then the client name. And then underneath that, let’s say Project A is the Vertical Inductor. So, we create a directory called “Vertical Inductor”. Alright. And under Vertical Inductor, we’ve got several directories. And what we try to do is keep these file names the same so that it’s consistent for everybody. Otherwise, you run the risk of people not knowing where the correct file is, which could be really, really bad. Because if you don’t maintain control over where files are placed, then you end up with names like . . . “12 February ’04”; “13 February ’04”; “29 November”; or, “Latest”; “Latest Old”, “Latest New”. So, you can imagine that someone stepping in who isn’t the person who created those directories is not going to have a clue which is the correct set of files. Same thing for the person who created them comes back six months’ later, may go, “Ah . . . I don’t know.” And the scary part is you might grab the wrong files. Let’s say you grab the wrong files and made some parts. You just made some scrap metal, potentially. Or worse than that, it may take you a while to figure out what’s scrap metal and what’s not, and that may be more expensive than just doing the whole thing again. So, in order to avoid that entanglement, what we do is to have a directory called “Current Design”. Current Design is the working directory. After the project’s over, the files in Current Design, theoretically, should be the latest, but may or may not. So, then . . . while the projects active, Current Design should always have the up-to-date files. And that’s not necessarily released, but that’s the current working files. And by working files, it means the ones you’re working on; maybe if you just released and maybe those are the latest (same as the released). But if you’re between releases and your current design is your . . . is the directory that you’re using to pull files out of.
Now, once you get a lot of hands working on a project, it’s always good to have a gatekeeper. And the gatekeeper is the person that controls what goes in Current Design. So, he may have ten people providing files to him; then he turns around and puts those in Current Design.
We also have a directory called “Released”. Released contains files that have been released. And what released means is its gone out to the vendor. Because most of the time we’re operating in a development mode, our release policies may be a little different than your released policies in a large manufacturing facility. Or in any manufacturing facility. Because what we do is every time a drawing goes out to a vendor, we bump up the Rev. In absence of a specific revision policy, what we do is we go up by numbers. So, we’ve got a part number, and then the revision starts at 00; goes to 01, 02, 03, 04, 05. So, we can have a release at 07 or release at 12, a release at 99.
So, one of the things is I think it’s important to keep in mind is that your revision number structure is something that someone eventually picks. And as long as it works for you it just doesn’t matter. It just needs to be consistent. You can do A.1, A.2; we’ve seen that. You can do . . . a major release as A, a minor release is numerical. So, it could be A.01 or A01. We just think it’s easier just to use 01, 02, 03, 04.
Now, whenever we release a drawing to a vendor, or send it out to someone who . . . may use that to make a part, then, if we make changes to that drawing, we revise that drawing. If the change is very, very small, i.e., does not affect the final result that you get back (and maybe it’s not rev’d at that point) . . . so, for example, if you add a comma to a note that cannot possibly affect the outcome of the part (it’s just to fix some grammar), then maybe you don’t release that if you’re in the middle of development. At the end of a project, everybody has drawings; I’m sure you’ll need to rev that.
So, the release directory . . . so, we’ve got a directory called Released, under our Induction directory. And so then underneath that, we’ll have “Rev (R-E-V) 01”. And so that’s our first release, when we first send out drawings to someone, or to the client, call it Rev 01. The next time we have a release, we’ll call it “Rev 02”. It’s important to note that part numbers and assembly-drawn numbers may not necessarily align with this Rev 02, Rev 03; it just means it’s the next time we released a set of drawings. Now, it may (depending on the client, depending on the client’s needs) there is a possibility that we may rev the assembly to match the top level assembly to match that revision in the directory. It kind of depends on where we are on the development process. But that way you always know that here is the latest and greatest that we’ve sent out. The . . . Release directory also gives you a historical reference for what you’re working on. So, that way you can go back and look at earlier versions of files if you need to. Hopefully you never need to, but if you have a corrupted set of files, or something along those lines, you could.
We also create “Concept” directories. And that Concept directories will then have sub-directories underneath that indicating which part of the project. So, maybe if you did . . . sketches for the rear-mount, or the fascia, they might have separate directories. Usually we name concept sketches by date, which seems to work well, but that’s up to you. So, usually what we’ll do . . . so, we’ll do “2014 Sept 24 – “ and then the name of the concept . . . “Rounded Fascia Concept”, not PDF or what-have-you.
If you have any questions about this, please don’t hesitate to give me a call. It’s kind of a long section here and technical, but happy to entertain your calls, questions. It’s 1-800-722-7987. That’s Montie Roland. Email – montie (M-O-N-T-I-E)@montie(M-O-N-T-I-E).com. Or you can visit our website – www.montie.com. You can see the results of client work we’ve done at the montie.com website. Or you can see some of our projects that we’ve done for ourselves at montiegear (M-O-N-T-I-E-G-E-A-R).com.
I hope this has been beneficial. Montie Roland, signing out.