How Accurate Are Analyst Price Targets?

Analyst targets in theory can streamline a lot of trade decisions. Target price is higher than the current price? BUY! Oh, if only it was that easy.

A 2012 study of 11,000 analysts from 41 countries found target accuracy to be fairly low. 18% for 3-month and 12% for 12-month price targets.

There are a number of reasons for the low success-rate.

1) Targets are based on point-in-time information. Predictions get stale fast when information changes - this happens often.

2) Conflict of interest is a concern. Analyst who have a vested interest in a stock might be bias. If you owned Tesla, you might be swayed to give a generous target.

3) There's no standard for how price targets are achieved. Every analyst has their own models and methods. Results can vary wildly.

4) There's no accountability. Analyst can be completely off and simply revise their target. No sweat off their backs.

5) Markets are volatile, especially in the short-term. They can swing for no reason. Markets are made up of us unpredictable beings. No matter how much data you have, it's hard to know what we're thinking.

6) And most importantly, no one can predict the future.

It's understood amongst professionals that targets aren't truth. They're simply a signal. A way to sense how Wall Street is feeling about a stock. It's an interesting data point but not something you trust at face value. Next time you see an opportune price target, think twice before diving in.

Comments

Today's Special: Humble Pie

You champion a project, fight for an idea, and then...reality sets in. That churning in your stomach isn't butterflies, it's the realization you've missed the mark. Pride will puff up your chest, and kick in the "defend at all costs" instinct. But arguing with the umpire never changed a call. Admitting you're wrong isn't a sign of weakness. It can strengthen your professional standing. In a world obsessed with the illusion of infallibility, the courage to adjust course is a breath of fresh air. It shows you're confident enough to be wrong, and adaptable enough to learn from it. Do your research, think critically, and stand behind your decisions. But when the data whispers (or screams) otherwise, don't be afraid to swallow that slice of humble pie. Be the first to acknowledge. Don't wait for someone to point out your mistake. Be open, take responsibility, and most importantly, focus on what you're going to do to address it. Don't dwell ...

Starting Really Really Small

On your desk is one of the most intimidating sights known to man. A blank page. The prospect of filling it up with anything resembling decent seems insurmountable. Staring at the long road ahead fills you with anxiety and dread. The first step is the most difficult. So we procrastinate. We " research ", we " prep ", we " plan ". We do everything except tackling the problem. We avoid the pain for as long as we can. To make a blank page less intimidating. Tear it in half. There, half as scary, twice as easy. Still too much? Do it again. And again. Keep doing it until the task is so small that it's too easy not to do. Getting starting is the hardest part. So make the hardest part as easy as possible. This doesn't guarantee amazing results, but it gets you in the game. You can't win if you don't play.

Why We Shouldn't Be Afraid of Ambiguity

Ambiguity. That fuzzy monster that chases us down darkened hallways, whispering doubts about our roadmap and feature sets. You know the feeling. You constantly wrestle with unknowns: Will users like this? Is this the right direction? Frankly, if you had a nickel for every time the answer wasn't crystal clear, well, you might actually want to chase that ambiguity down the hall. But here's the thing: ambiguity isn't your enemy. It's your dance partner. Innovation rarely happens in a land of perfect clarity. Sure, there's a time for well-defined processes. But when you're creating something new, there are bound to be more questions than answers. The key is to learn to waltz with the unknown . Embrace the experiment. Don't be afraid to throw some spaghetti at the wall and see what sticks. Focus on outcomes, not outputs. Don't get hung up on features. What problem are you trying to solve? How will you measure success? Get comfortable with "go...

Herman Ye

Search