1. Lack of faith in team (caused directly by issues 2,3)
- Over the past weeks and certainly days there’s been increasing negative sentiment, with people not believing the team or trusting in them. This has escalated over the past c.48 hours with the IDO.
2. Poor communication from team
- Many members of the community have highlighted that communication has been lacking on both key issues and minor updates. There’s been little effort to group core updates in one place, bar Jeus’ weekly updates. We’re left picking crumbs up from the AMAs, which themselves have done little to inspire confidence over the past 24 - 48 hours.
3. Lack of clarity
- I believe this to be the principal issue. The community don’t understand where the project is going right now, or why decisions are being made. There’s either absolutely no reasoning provided for decisions, or decisions being made with reasoning that doesn’t fit with the community’s beliefs / feelings. This, and the issues it creates is illustrated beautifully by the IDO - as I write this it’s 2.49% sold out and has been live for 90 minutes; hardly a rapid sellout.
—> Let’s dig down into why that is. I see two reasons.
- On the one hand we’ve got the community - already invested, and eager to support. However, they weren’t told about this IDO in time, and even if they had been, they’d be unlikely to support it. It doesn’t fit with what they want, and doesn’t make sense. The justifications made for it seem to mask a cash grab, rather than inspire confidence. The reasons for it being on BSC remain confusing, and I can’t help but think it’s simply because there were pre-existing relationships in BSC that it was felt would be easy to milk for quick cash.
- On the other hand, we haven’t got a huge influx of new investors. Could be because of the bear market. Could equally be because people did their research, and looked into the project. They saw a token that’s seemingly headed to 0, floor prices that have dropped 10X in a couple of months, and reasoned that this wasn’t a good investment.
1. The team needs to provide more information to improve investor confidence. That information needs to be readily available.
- Father — ‘You don’t need to know yet exactly what he does, but you will, soon.’
At this point, we need to know exactly what he does. More to the point, it would be good to know what he has done.
Eugene — Chief Product Officer
Eugene provided some info on his past experience in the AMA yesterday - why not put this on the website?
Dima (Memological Expedition/MEMEXPO) — Chief Technology Officer
Jeus (brother) — Your guide/big brother in the Colony, but don’t call me Oniisan (CCO)
Jeus I know you’re unwilling to Doxx, but maybe this is what’s needed to get people back on side?
Ivan (Lyagushka) — Product lead
Marx (Mike) — 3D artist
Woolly — 2D artist
Karina — UI artist
Nadia — Gameplay writer
Interested to know more of what this involves.
Ilia — Developer
Maxim — Developer
Nikita — Business development
Rey — Business development
Andrey — Business development, security advisor from Zerion protocol
3 Biz Dev (+/- Father) vs 2 devs. Is this the right approach?
2. The team needs to listen to the community and introduce clear communication protocols.
There’s a lot of project managers, founders, business owners, etc, in the community - who are justifiably confused by the lack of clear comms. Let’s have a clear protocol that is stuck to. Be that weekly stand-ups for the community, some core parts of / highlights from check-ins being conveyed to the community, all-hands meetings that are videoed - find what works and do it. It’s been a long time since we started asking for better communication, and still nothing. AMA’s have to have a précis that people can glance over each time. This feeds into the next part.
3. Clarity: an easily accessible roadmap, honest discussion of recent decisions
We need a roadmap - right now we don’t have one that we can trust. What features are actually coming, and at what points? Again, the community aren’t idiots, they know that bringing out new features is tough and takes time, and that exact dates can be hard. We just need to know the prioritisation of features, and a very rough idea of when we might expect them. If you’re using sprints, maybe share an overview of each sprint.
We need a clear rationale for why certain recent decisions have been made, chiefly the IDO. We need to feel the team is now on the same page regarding them, rather than there being a difference of opinion.