š Road to Launch #2 - Channeling Community Feedback š
Greetings, heroes of Songs of Silence! āļø
We continue with our Road to Launch series - giving you this week an insight on HOW exactly we listened to Community Feedback (you!) to build āØ Songs of Silence. āØ
Yes, that's right! An DIRECT INSIGHT into Game Development. š ļø
Full disclaimer - what we're about to show might seem "cryptic" at first š¤ But it makes sense.
Also - This does NOT take into account bug reports. š We could (should?) make a dedicate news on that one.
[h2]š Trust the Process š[/h2]
Before addressing anything, our team needed a CLEAR PROCESS.
This is taken from our internal Miro board. We used it before going into Early Access to define how we would channel Community Feedback.
To break it down ...
[h2]š Collection š[/h2]
Players need a space to express themselves! Say what they like š¤ or don't like. šµāš«
We chose to focus on 3 SPACES.
Through these 3 spaces, we received close to 200 pieces of UNIQUE feedback. š± This doesn't take into account whether people agreed or not with what others were saying.
Long story short - We receive A LOT of highly pertinent feedback. Much food for thought! š
[h2]š Consolidation š[/h2]
All this feedback needed to be ā”ļøaggregated in 1 placeā¬ ļø.
Time for things to become very corporate. š¼ We used a good ol' Excel sheet.
Note - the list goes on and on and on ...
[h2]āļø Decision āļø[/h2]
Sadly I don't have any pictures to share with you here... š
But in a nutshell, we gathered once a week (more in the first days of Early Access) to discuss what the š„ HOT š„ topics were in the different spaces.
We'd then decide on what to tackle first, based on the following questions - in that priority. š
This then determines - in a very unemotional manner - what we tackle first.
[h2]š ļø Implementation š ļø[/h2]
Alright, we all agree on what we must do! š¤ Now comes the fun part.
We log the tasks into our tracking software as tickets š« and off the Devs go!
A few weeks later, out come the fixes, content or features. Hot like a fresh load of bread. š„
And everybody is happy. š„³ (at least in theory hehe)
And that's all for today folks! š«”
We hope you're as excited as us for 1.0 Release on November 13!! š¤©
https://www.youtube.com/watch?v=iKwhf7G7cpk
āļø See you on the battlefield! āļø
Cheers,
The Chimera Team
We continue with our Road to Launch series - giving you this week an insight on HOW exactly we listened to Community Feedback (you!) to build āØ Songs of Silence. āØ
Yes, that's right! An DIRECT INSIGHT into Game Development. š ļø
Full disclaimer - what we're about to show might seem "cryptic" at first š¤ But it makes sense.
Also - This does NOT take into account bug reports. š We could (should?) make a dedicate news on that one.
[h2]š Trust the Process š[/h2]
Before addressing anything, our team needed a CLEAR PROCESS.
This is taken from our internal Miro board. We used it before going into Early Access to define how we would channel Community Feedback.
To break it down ...
- Collection - Offer spaces where people can post and express their opinions š
- Consolidation - Once or twice a week, feedback is agregated into a single Excel Sheet š
- Decision - The sheet is reviewed by a leadership commitee, to align on priorities āļø
- Implementation - Tickets in JIRA (game dev tool) are created to track & address priorities š«
[h2]š Collection š[/h2]
Players need a space to express themselves! Say what they like š¤ or don't like. šµāš«
We chose to focus on 3 SPACES.
- Steam Forum
- Discord
- Our own Reddit-like website
Through these 3 spaces, we received close to 200 pieces of UNIQUE feedback. š± This doesn't take into account whether people agreed or not with what others were saying.
Long story short - We receive A LOT of highly pertinent feedback. Much food for thought! š
[h2]š Consolidation š[/h2]
All this feedback needed to be ā”ļøaggregated in 1 placeā¬ ļø.
Time for things to become very corporate. š¼ We used a good ol' Excel sheet.
Note - the list goes on and on and on ...[h2]āļø Decision āļø[/h2]
Sadly I don't have any pictures to share with you here... š
But in a nutshell, we gathered once a week (more in the first days of Early Access) to discuss what the š„ HOT š„ topics were in the different spaces.
We'd then decide on what to tackle first, based on the following questions - in that priority. š
- How bad is it impacting players?
- How often does it happen?
- How difficult is it to fix?
This then determines - in a very unemotional manner - what we tackle first.
[h2]š ļø Implementation š ļø[/h2]
Alright, we all agree on what we must do! š¤ Now comes the fun part.
We log the tasks into our tracking software as tickets š« and off the Devs go!
A few weeks later, out come the fixes, content or features. Hot like a fresh load of bread. š„
And everybody is happy. š„³ (at least in theory hehe)
And that's all for today folks! š«”
We hope you're as excited as us for 1.0 Release on November 13!! š¤©
https://www.youtube.com/watch?v=iKwhf7G7cpk
āļø See you on the battlefield! āļø
Cheers,
The Chimera Team