Phylogeny

A phylogenetic tree (or cladogram) is a picture of evolutionary relationships, and the single idea to hold onto is that relatedness is read at the nodes — the branch points where lineages split from a shared ancestor. Two tips are more closely related when the most recent common ancestor they share is more recent. That is a fact about the branching pattern, and it has nothing to do with how far apart the tips are printed along the top of the diagram.

The second big idea — the one graders love to test — is that the left-to-right order of the tips carries no meaning. Every branch can pivot freely at its node, like the arms of a hanging mobile. You can swap the two branches at any node, reshuffle which tips end up as neighbors, and the tree still says exactly the same thing. Only the connections — who shares an ancestor with whom — encode the relationships. Tips that end up side by side are not automatically each other's closest relatives.

Hold onto two contrasts and the rest of the topic follows: nodes set relatedness, tip spacing does not (trace back to the shared branch point, never eyeball the gap between tips), and “more derived” is not “more evolved” (a lineage with newer traits is not higher or superior; every living tip has evolved for the same span of time). Keep those two straight and a tree stops being a ladder and becomes what it really is — a map of shared ancestry.

Reading a phylogeny is not about scanning the row of tips; it is a short procedure you run at the branch points. Walk the steps in order and the relationships fall out the same way every time — no matter how the tree happens to be drawn.

1. Find the tips and the nodes. The tips are the taxa being compared (often living species); the nodes are the branch points where a lineage splits. Each node represents a most recent common ancestor of everything above it. The pattern of nodes — not the spacing of tips — is the information.
2. To compare two taxa, trace back to their shared node. Follow each lineage down until the two paths meet. That meeting point is their most recent common ancestor. The more recent that shared node, the more closely related the two taxa are.
3. Ignore how close the tips look. Two tips can be printed right next to each other yet share only a very deep, ancient ancestor, while a tip drawn farther away shares a much more recent one. Physical adjacency along the top is a drawing choice, not a relationship.
4. Remember branches rotate freely. At any node you can swap the left and right branches. This reorders the tips but changes no relationship — the tree is a mobile. If a “fact” about the tree disappears when you rotate a branch, it was never real.
5. Group by shared derived characters into clades. A branch and everything on it — an ancestor plus all of its descendants — is a monophyletic group (clade), defined by the derived characters that arose on that branch. Clades nest inside clades; that nesting is what the tree encodes.

Notice the through-line: every question about relatedness is answered by tracing lineages back to a shared node, never by eyeballing the gap between tips. The branching pattern is the meaning; the layout on the page is just presentation.

Quick reference card. For each term, read what it is and where students most often trip — the recurring theme is that relatedness lives at the nodes, and being “more derived” is not being “more evolved.”

Almost every phylogeny mistake is one of two reflexes: reading relatedness off the gap between tips, or reading a lineage's novelty as a rank. Both feel intuitive and both are wrong. Naming them makes them easy to catch.

Relatedness is not tip proximity. The single most common error is to say two taxa are closest because their tips sit next to each other along the top. They are not. Relatedness is set entirely by the most recent common ancestor — the shared node. Two tips can be neighbors on the page yet meet only at a deep, ancient node, while a tip drawn far to the side meets one of them at a much more recent node. Always trace back to the branch point; never measure the horizontal distance.

Branches rotate, so tip order is meaningless. Because you can pivot the two branches at any node without changing the tree, the sequence of tips along the top is arbitrary. Anyone who reads “neighbors = relatives” will get a different answer just by flipping a branch — proof that the reasoning is broken. The connections are fixed; the layout is free.

“More derived” is not “more evolved.” The second trap treats a lineage with many new (derived) traits as higher, more advanced, or superior — and often assumes the rightmost tip is the “top” of the tree. But “derived” only describes a trait as newer than the ancestor's version; it says nothing about worth. A tree has no top rung.

Every living tip is equally evolved. All the tips alive today are separated from their common ancestor by exactly the same amount of time. A bacterium and a beetle have each been evolving for the identical span since they diverged — neither is a “primitive” leftover or a “higher” achievement. Keep these ideas straight — nodes not tips, branches rotate, derived is not superior, all living tips equally evolved — and phylogenies stop tricking you.