Frame-Building: Part 1 - The Why

It's complicated. Sort of.
When I started racing mountain bikes, converting from BMX, the types of suspension designs, geometries and materials were dizzying. I was cheap, and sponsorless, so my racing rigs were whatever the local guys were willing to sell me on the cheap.
In hindsight, I built up some sketchy bikes that got me through each racing season. Riding bikes was obviously what excited me, but I found more and more that the subtle changes in each new bike were what had me diving headfirst into engineering.
How can 5mm up or down on the handlebar height make that much of a difference?
Why do lower bottom brackets create such a stable ride feel?
Do we really need multiple gears on the cranks?
When I learned AutoCAD and SketchUp, I found that suddenly I could experiment with all different types of designs, and I spent almost as much time tinkering on the computer as I did riding my bike.
Then came the drilling and machining, because I rarely leave well enough alone.
I made some insanely sketchy mods on my Azonic Eliminator to increase the compression ratio in the last 30% of shock travel. I shortened some no-name cranks to 160mm. I turned a QR135 Jamis Dakar into a fully threaded 135x10 thru axle that was only, like, 2° off square.
Most of these mods miraculously resulted in very few failures/bodily harm.
Back then I thought I could go and start a bike company, but at the time I lacked the connections and tooling to properly test things, so instead I just continued to dream things up on paper. At that age, getting the tooling, fixtures, and materials to test these ideas would have cost tens of thousands of dollars.
Today, consumer-level fabrication has never been more accessible, and gaining an applied knowledge of how to do these things only requires an internet connection and a bit of time.
Add that to my still-relentless "fuck it, let's give it a try" attitude, and maybe I can make my childhood dreams come true.
A few years ago I used the price-accessible builder we all know and love down in Peru to experiment with some frames that had, at the time, radical geometry ideas. After a few iterations, I realized I was onto something, and so I started to develop a new design philosophy.
Geometry: just a bunch of numbers
Most bike companies will put up this little graph next to their frame's specifications that lists out the geometry. I think most people don't really understand what these numbers mean; they just know that they equate to the way the company says the bike will ride. These companies don't often go in radically unique directions with geometry, at least not relative to other companies. Each year you can scan all of the "trail bikes" from various brands and see pretty much the same geo across the board.
There are a handful of trendsetters where you'll see "production geo" for the masses, these are the big brands that we all know. Then you may have some smaller manufacturers that push the bar a little bit with more "progressive" numbers. These are usually things like slacker head angles, longer or shorter chainstays, or more adjustability for you to tune your ride.
To help, here is a general list of common geometries, what they describe, and what changing them means.
Head Angle (HA): This is an angular measurement of the head tube, as if you were to draw a line straight through the head tube and down to the ground. Bikes have a range of head tube angles, roughly from 62° to 75°. A steeper head tube angle (higher number) generally results in less stability at speed and quicker steering. A slacker head tube angle (lower number) generally results in more stability at speed and slower steering.
Seat Tube Angle (SA): This is an angular measurement similar to HA, except you draw that line through the seat tube and down to the ground. Generally speaking, a slacker seat tube angle will provide a more laid-back and less efficient pedaling position, and a steeper one will do the opposite. Sometimes you'll have an "actual" seat tube angle and an "effective" one, normally when the tube is offset in some way.
Seat Tube Length (ST): This is a direct measurement from the center of the BB to the top of the seat tube. Some companies measure to the center of where the top tube intersects the seat tube (center-to-center), and some measure to the top of the top tube (center-to-top). This is most commonly associated with sizing frames for different-height riders: shorter for shorter, longer for taller.
Top Tube Length (TT): This is a direct measurement from the center of the seat tube to the center of the head tube. This used to be one of the main measurements used to help describe fit and feel of a bike. In essence, the longer the top tube, the longer the reach to the bar; the shorter the top tube, the shorter the reach. So longer-top-tube bikes tend to be better suited for taller people.
Bottom Bracket Height (BB): This is a measurement from the ground to the center of the bottom bracket. This measurement is important in the context of another: BB drop, which means the position of the BB relative to the imaginary line between the axles of the wheels. Generally speaking, the lower the BB, the more stable the bike tends to feel at speed.
Chainstay Length (CS): This is a measurement from the center of the rear axle to the center of the bottom bracket. It is sometimes referred to as "rear center", opposite of front center, which describes the BB-to-front-axle measurement. Chainstay length determines a good bit about the ride characteristics relative to other geometries, but typically: a shorter chainstay is more agile in corners and allows the rider better maneuverability when there is a bias of weight on the rear wheel—think manuals and bunny hops. A longer chainstay is generally more stable at speed, and typically less agile as a result.
Wheelbase (WB): This is a simple measurement between the center of the front and rear axles. Mostly, you can expect shorter wheelbases to be agile and longer ones to be stable.
Wheel Size: To my knowledge, not many consider wheel size to be in the category of geometry, but I think it belongs in the conversation more than almost anything else. Generally speaking, bigger wheels are harder to speed up and slow down, and smaller wheels are the opposite. More on this later.
Compound Geometries
Reach: distance from the BB vertical line to the top head tube centerline.
Stack: distance from the BB horizontal line to the top head tube centerline.
Effective Top Tube (ETT): distance horizontally from the top center of the head tube to where that line would intersect the seat tube angle. Reach, Stack, and ETT are mainly used to translate fit across different brands.
Trail: the horizontal distance on the ground between where the steering axis intersects the ground and the tire's contact patch.
There is more, but this should give you a basic understanding of geometry before we dive further in.
Something better, and something worse.
As mentioned above, changing geometry measurements changes the ride characteristics of the bike. That would likely be obvious without understanding any of the above.
There is a complex relationship between all of these geometries though, and while changing one does have direct results relating to that measurement, it also has an effect on almost everything else. If this seems complicated, it is.
Bike geometry is a really difficult thing for most people to wrap their heads around. I think you may be surprised to hear, dear reader, that a lot of product managers don't truly understand geometry either, at least not right away.
I'd like to make this a bit easier. To do that, we are only going to focus on two things: Center of Gravity (CoG), and force.
Don't worry, we aren't going to do any big math or formulas here. We're just going to do some visual experiments.
Let's imagine a bike with massive wheels that are pretty close together, just enough space for a rider to sit comfortably. Set them moving, and then apply force to them by riding over a bump in the terrain.

AI Helped me with this image, and I think it did a great job.
At slow speeds, not much happens; the rider can pedal over this no problem. At fast speeds though, this small bump becomes much less stable, because the force of the impact is greater and the rider's CoG is much higher.
It's easier to tip a triangle with a height taller than the width of its base.
Now let's imagine a bike with really small wheels that are very far apart. Set the rider on there and give them a push. Now give them the same bump as earlier.

AI Helped me with this image, and I think it did an okay job.
At slower speeds, the bike may come to a stop because getting the smaller wheels over it may require substantially more effort. At faster speeds, that little bump may cause the bike to get airborne. Since the rider's CoG is low relative to the long wheelbase, they may get jarred around, but ultimately remain on the bike.
It is harder to tip a triangle with a base that is wider than its height.
How about a normal trail bike, but sized XL? Put a short rider on that, and then put a tall rider on an XS. Because of the differences in CoG relative to the bike, the shorter rider will have a hard time maneuvering the larger bike regardless of the riding geo; similarly, the taller rider will feel highly unstable on the smaller bike regardless of the riding geo.
On each of these extremes, it doesn't so much matter what the head tube angle is, or really any of the other measurements. We've exaggerated two geometries to the point that the ride quality is firmly established.
What happens if that first rider on the massive-wheeled, short bike decides to move around, though? What if, before they hit the bump, they unweight the front wheel by shifting their CoG back, and then immediately shift it forward to hop over the bump entirely?
The rider's behavior suddenly hits the override switch on the stability of the bike.
Are riding characteristics solely about geometry anymore?
The point here is that most of what we experience as geometry evolution over the years has been small experiments in one or two areas, but rarely the geometry system as a whole.
Can't see the Force for the trees
The vast majority of bikes out there are designed around a relatively fixed rider position. Sizing is like this, and so are all of the measurements we discussed above.
But a mountain biker isn't a fixed point.
There are a lot more forces that come into play with mountain biking than the ones most designers focus on. A big one that I think gets lost in the geometry conversation is the force vector.
We saw two examples of force vectors earlier, with the large-wheeled and small-wheeled bikes. Essentially, a force vector describes both the magnitude and direction of a force.
Now hold on a second, because you may never have heard this term before, but trust me:
How enjoyable your bike ride is comes down to how you and your bike handle force vectors. It always has, and it always will.
Have you ever hit something that made you go over the bars? Surprise, force vector.
Ever hit a jump? Force vector.
Charged through a rock garden? A whole shit ton of force vectors.
To be more visual: imagine a circle rolling toward a small, square-edged bump. The bump's height represents a small fraction of the height of the circle. When the circle contacts the corner of that bump, its axle has to move both forward and upward for the wheel to pass over it.
Make the circle larger and the path the axle needs to follow becomes shallower. Make the circle smaller and that path becomes steeper.That's the real advantage of a larger wheel over an obstacle.
The idea behind larger wheels being "smoother" isn't magic, it's geometry, and it's not the whole story. Wheel size genuinely doesn't matter as much as you've been told.
Hold up, koolaid drinkers, just hear me out.
It's important, just not in the way you probably think it is.
Breathe, just breathe. We can do this.
There has been research done about this, but normally it is next to a bike company trying to sell the hill they are willing to die on. I just want to explain my design philosophy a bit more in depth.
Let's look at a 26" wheel and roll it toward a common 3" root on a trail. We'll assume that root is essentially square. At point of contact, this wheel has to initially climb over an angle of about 39.7°. Now do exactly the same thing with a 32" wheel.
The 32" wheel encounters that same 3" root at a 35.7° angle. Now sure, that is technically a mechanical advantage, but you increased the wheel size by 23% to get a 10% reduction in climb angle. As obstacles get larger relative to the wheel, that advantage becomes increasingly important. In other words, the biggest benefits of the bigger wheel show up as the terrain gets chunkier. The last time I checked, though, the rocks on the trails I ride haven't gotten bigger.
Come on y'all, its math.

Here's the part I think gets lost though:
The wheel only determines the geometry of that initial interaction. The whole bike determines what happens as you try to roll over it.
That isn't the whole story though. As I said, wheel size is important, just not in the way you
may expect.
I'm not saying I am building a bike with 32" wheels, nor am I building it with 26" wheels (though I gave it some serious thought). In point of fact it will be a dual 27.5" wheeled bike. I'm just saying that we as riders are often sold a measurable improvement in one characteristic as though it represents an improvement to the entire bike.
The big picture
I hope that by now, the wool is out of your eyes and you are maybe thinking a bit more objectively about that $8,000 bike you bought this year, and the $7,500 one you got last year, and maybe the $7,000 one before that.
I'd like to run you through another experiment to show you just the extent that two geometries can have on riding characteristics.
Just a quick elaboration of our first geometry measurement that we discussed: head angle.
I mentioned that a slacker angle is generally more stable at speed, and a steeper one generally quicker to steer. But even that isn't really the result of head angle alone. Change the head angle and you also change things like trail, front-center, wheelbase, and the relationship between the wheel's contact patch and the steering axis. If we imagine that same experiment earlier with the 26" and 32" wheel - the larger wheel with a super steep headangle has a lot more potential to send the rider over the bars than the smaller wheel with a slack headtube angle.
There's that annoying system again.
Think of the wheels in relation to the rest of the bike less like they are individual rotating masses that "roll" over things, and more like two points of a line that want to move parallel to the ground at all times.
Wheel size, then, determines how high that line is off the ground and where the wheels contact obstacles. Bike geometry and the rider's CoG determine how the loads from those obstacles get managed.
A large wheel may hit the same obstacle at a more favorable angle, making it easier for that point to continue moving forward, but that's only one part of the system.

AI helped me create this image, and I think it did an okay job.
It's challenging to wrap your head around, I get it; and we haven't even added suspension yet. That makes things a lot more complicated.
I like it though. This is the sort of complex system that I enjoy taking apart and examining; and when I do so, I am able to remove the vestigial concepts and rebuild it into something new.
A New Design Philosophy
I realize that was a lot, but it's necessary to understand the perspective that I designed this frame from.
I mentioned earlier that most manufacturers are designing for a range of riders; the "production" geometry is meant to suit a huge number of consumers. That sort of means that in order for the bike to be ridden as intended, those riders all need to have the same style.
Well, you probably guessed it: I do not have a normal style of riding.
When I ride bikes, I move a lot. I shift my weight around constantly in relation to not just the terrain, but what I am trying to do over the terrain. My style is very much that of a mountain biker who rode a lot of BMX and trials in his youth. Climbing to me isn't just about pedaling hard. It's hopping, pivoting, preloading, and twisting. I pop off of everything I can. I manual through tight trees and turn my bars at the last second to clear them. I land bunny hops immediately on the gas. I explode up technical climbs.
I have a precisely messy riding style. I want to clearly know the limit of traction, speed, and clearance of my bike so I can keep it right on that line.
Riding this way on a production bike was always really challenging, so any mass-produced bike I got usually ended up with a unique build: offset bushings, longer or shorter travel fork, wider or narrower tires, shorter cranks, etc.
What if, though, I specifically designed a bike around that riding style? What would it look like?
Need to haves:
Stable at descending speed
Pedaling efficiency
Enough suspension to handle most trail riding
Agile and playful
Nice to haves:
Strong and durable
Simple and maintainable
I think I designed that.

In Part 2, I'll talk about how I designed the frame, and some of the challenges I hit while creating this system.

![Writer: TroubleMake[r]](https://static.wixstatic.com/media/471d6f_4e4e931eae9c4a5c9b5ddb0fb7ff2c40%7Emv2.jpg/v1/fill/w_32,h_32,al_c,q_80,enc_avif,quality_auto/471d6f_4e4e931eae9c4a5c9b5ddb0fb7ff2c40%7Emv2.jpg)



Comments