I don't want to be negative, but this really feels like a dangerous strategy. No, that's nice, this feels like a mistake and this person with a C-title is lead

I don't want to be negative, but this really feels like a dangerous strategy. No, that's nice, this feels like a mistake and this person with a C-title is leading them into a trap. - This company is semi-old (they've survived a generation) - They are heavily built on reference and recommendation - Their prior name has an above average reputation - Their name's source has a positive connotation with programmers, developers, and most of the code world ("we might go a little slow, but we catch small details. We have less bugs") - Change is bad - People hate change - People don't care about 'mission statements' - Is your product/service good? - Can I easily find/contact you to get it? - Change is confusing - Mental links - Physical links - Resource, supply, pointer, ect.. links - Makes you hard to find - Wishy washy 'let's hold hands' change is worse - As leader, I don't really know what I want - Getting ideas, brainstorming is great - Publically letting everyone know you have lost your way and are entering a period of company uncertainty - Not