I was sure Fretscape had picked the wrong fingering.

The annoying part was that when I looked closer, it hadn't.

I was testing an A minor to F change. A common beginner progression - and often the first time a player runs into a barre. I'd typed them in, clicked through, and stared at the screen. The fingering Fretscape had chosen felt wrong. Not a little wrong - clearly wrong. I was already halfway into "I need to fix the solver" when I stopped and actually looked.

It took me a while. But I got there. And that's when I realised I'd built something that had just corrected my own musical intuition.

TL;DR Fretscape picked the F fingering xx4312 for an A minor to F change when I expected xx4311. I was sure it was wrong. It wasn't - the less obvious fingering had two anchor fingers, and the cleaner-looking one needed a regrip into a barre. The tool spotted something my instinct had papered over. That's the whole point of the product, and it was the first time it had given me the kind of aha moment I'd built it to give other guitarists.

The idea Fretscape was built on

Most chord tools treat shapes in isolation. You look up a chord, you get a diagram, you move on. Whether you can actually get to that shape from the one before it - or leave it cleanly for the one after - is your problem.

Fretscape tries to optimise the movement between chords. Not just the shape under your fingers at the moment you hold it, but the journey from wherever you're coming from to wherever you're going next. A fingering that looks less obvious on paper can still be the better choice in context.

A chord fingering isn't just about how easy the shape is. It's about how easy it is to arrive there.

This sounds simple when you say it out loud. Most good ideas do but I couldn't find a tool built around that idea.

The original aha moment that started all this

Long before the A minor to F moment, I'd already seen the same idea in simpler changes. G to D, mostly. Including when I was trying to make guitar feel less frustrating for my daughter, Isla.

The familiar open G and open D are among the first chords most guitarists learn. Easy in isolation. But switching between them - even that switch - isn't as smooth as it looks. The hand has to reset. Fingers come off, different fingers go on, the whole shape reorganises from scratch.

There's another G voicing where the B and high E sit at fret 3. It looks more awkward on paper. 4 fingers versus 3, that's intimidating for a beginner! But the move from that G to open D is smoother because it gives you that stable anchor finger when transitioning.

Experienced guitarists do this instinctively. Once a shape lives in your muscle memory, though, it's hard to let go of it - even when there's a better option waiting. So I kept asking myself: why isn't there a tool that helps with this?

That question is the whole reason Fretscape exists.

The progression that made me question the solver

Back to the A minor to F moment.

I'd set up two chords. A minor, then F. Fretscape kept the A minor voicing I expected - x02210, standard shape, no surprises. For F it chose xx3211, the small four-string F. Fine. That's the sensible linked voicing for a beginner-friendly A minor, and anyone who's ever learnt this progression has met it.

Then I looked at the fingering Fretscape had picked.

xx4312.

Pinky on the D string at fret 3. Third finger on G at fret 2. First finger on B at fret 1. Second finger on high E at fret 1.

My immediate reaction was no. That's not right. It should be xx4311 - pinky, third finger, and a partial barre on the first fret covering B and high E with the same finger. That's the fingering I'd been playing for twenty years.

Why I thought it had to be wrong

xx4311 looks cleaner. A classic small-F shape. One finger doing two jobs at fret 1, neat and familiar.

It felt more proper. It was easier in isolation. It was the familiar small-F fingering I'd trusted for years.

So my assumption was the obvious one: the optimiser had underweighted something. A cleanliness score, maybe. Or the cost of using the pinky. Or the general "a barre isn't actually that hard" factor that every beginner's guide tells you to push through.

Questioning the model was the right instinct. You should question the thing when it tells you something surprising. What I got wrong was assuming the model was going to lose.

What the optimiser saw that I didn't

Here's the bit I missed.

In the A minor shape, your first finger is already on the B string at fret 1. Your third finger is on the G string at fret 2.

Look at xx4312:

• First finger: B string, fret 1. Same place.
• Third finger: G string, fret 2. Same place.
• Second finger changes string, one fret back - from D2 to E1.
• Pinky drops onto D string, fret 4.

Two fingers don't move at all. One shifts a short distance to a new job. One new finger comes in.

Now look at xx4311:

• Third finger: G string, fret 2. Same place. That's the only one.
• First finger: was on B string alone at fret 1. Now has to flatten into a barre across B and high E at fret 1.

That re-forming of the first finger is a regrip. A small one - you're not moving it anywhere new, you're changing what it's doing. But it's a job change mid-progression. Your hand has to reshape, not just re-anchor.

xx4312 kept more of the hand where it already was. xx4311 asked one finger to change shape. The prettier fingering involved more work than it looks like it does.

The optimiser wasn't choosing the neater fingering. It was choosing the lower-movement one.

The moment it flipped for me

I went from that's wrong, to hang on, to I think it's right.

Then, finally: I've built something that just corrected my own musical intuition.

That wasn't a debugging moment. It was a product moment.

I'd spent months talking about the aha moment Fretscape is meant to give other guitarists. The feeling of looking at a fingering you didn't expect and realising, actually, yeah - that's better. The insight that lives in your hands the next time you play the progression, not on a diagram on a screen.

This was the first time the product had given that moment back to me.

Not because it agreed with me. Because it could disagree with me and be right.

Why this matters more than one chord change

This isn't really a story about A minor to F.

It's a story about why transition-aware fingering matters. Guitarists - all of us - judge chord shapes by how they look when held still. We look at the diagram, we check the reach, we feel the stretch, and we call it easy or hard. That judgement is about the chord as a photograph.

Real playing happens in motion. Chords arrive from somewhere and leave for somewhere else. A shape that feels easy in isolation can be a nightmare to get in and out of. A shape that looks awkward can sit perfectly in the context of the change.

That gap - between the chord as a photograph and the chord as a moment inside a movement - is where Fretscape lives. It's trying to help you see the moment, not just the photograph.

What I took from it

Good systems should be questioned. That's the first thing. You shouldn't take a recommendation on faith, whether it comes from software, a teacher, or a book. But you also have to be willing to find out the answer might not match your instincts - and do it anyway. Questioning is half the job. The other half is being honest about what you see when you look.

Explainability matters. The reason I could cross over from "that's wrong" to "I think it's right" is that I could look at the change and see what was actually happening. If Fretscape had just told me "trust me, xx4312 is better" and left it there, I'd have spent the afternoon rewriting the solver. The fact that the answer is legible - that I can see two fingers stay put where I thought one would, and that a partial barre isn't free - is what made the flip possible.

And this one's the big one: I wasn't trying to build software that copies my instincts. I was trying to build software that can reason past them. Copy-my-instincts is just me in a faster wrapper. Reason-past-my-instincts is a tool that actually does something.

I'd rather be useful than impressive.

Fretscape started with an aha moment

Thankfully, Fretscape's rebellion began with an A minor to F transition rather than the end of humanity.

The whole project grew out of one idea: context matters more than isolated shapes. And then, somewhere in the middle of development, the product proved that idea back to its creator.

Fretscape started with an aha moment about chord changes.I just didn't expect the next one to be for me.

This is one of five How Fretscape Thinks posts - each one about a moment where the easy answer and the right answer didn't agree. The others: the optimiser bugs I found while taking a screenshot, a ranking system that was correct but read wrong, why the right chord name has to be ranked first, and a key detector that knows when it doesn't know.

A few questions this raises

Why do guitarists stick with easier-looking fingerings even when they're harder to play?

Muscle memory, mostly. I did it for twenty years. Once a shape lives in your hand it's hard to let go of, even when there's a better option waiting. Doesn't help that most guitar books show you one fingering and call it the right one.

What's the difference between an easy chord shape and an easy chord change?

A shape is what your hand does when the chord's held still. A change is how much your hand has to reshape to get there from the chord before. A shape that looks comfortable on paper can still be a nightmare inside a progression - because every change forces a full reset.

Can software actually understand fingering difficulty the way a guitarist does?

Close enough, yeah. The physical cost - stretch, barre type, regrips, which fingers move - is measurable. Software tracks it without ego or habit, which is both its weakness and its strength. It won't pick the shape you grew up with. Sometimes that's exactly what you need.