Hey folks!
This year, I decided to finally bring my idea to life. The MVP creation is in progress, I believe the idea is cool, the logo is cool, the product is starting to work and becomes cool too!
I created a landing page, which aims to validate if others are interested in the idea and to create a list of early users for the beta program.
The key areas for feedback would be: explanation of the product, signup.
The site is available under: https://feedbucket.io/
All feedback is welcome: the good, the bad and the ugly!
Hey, the general idea and problem is clear.
However I've a little trouble to grasp what IS the kudos-box? Is it a positive text message? Or a physical thing? Or something else?
Having one or two specific examples would work wonders.
Good look with your journey!
It didn't come to my mind at all that it can be understood as a physical thing. That's some actionable feedback for me 🙇♂️
Thanks for taking a look!
Hey Brunc. I'm a SaaS copywriter. Here are my thoughts on your landing page.
First of all, I find 2 terminologies on the landing page. "Feedbucket" & "Kudos Box." This creates confusion.
People coming to your landing page are looking for a solution to their problems, right? If so, the landing page has to clearly state the solution. Especially in the headline. Because almost everyone is going to read the headline first.
And an interesting fact for you. Usually, headlines make 80% of sales. So you need to have a strong headline to make sales.
When a prospect enters your landing page with a strong headline, they are going to get a lot of doubts.
Doubts like "how easy is it to use?" or "how is this going to affect my productivity?" or "how is this going to improve my results?" and so on.
So on the rest of the landing page, you need to clear all these doubts. Once you do, that sales will happen. People will join your beta program.
Here's my conclusion
Thank you @agilan for your thorough analysis. This really resonates with me and gives me some food for thought and... room for improvement :)
This sounds like a great idea to help team building and motivation. To check if it's clear I'm writing my understanding of the site based on the landing page.
If I've got it right, by creating a team you can go to a specific team webpage under the feedbucket site where feedback for the whole team will be posted at a pre-determined time for the whole team to see and access. What's not clear to me is how a team 'manager' would add other members of the team, presumably by inviting team members to give their email as well?
I really like the idea of batched feedback but I'm not sure if motivating members of the team to check the feedback would be a challenge. I see that you send nudges and reminders and I suppose that motivating the team does to some extent have to come from the team manager.
Hope this is helpful!
Your understanding is right, thanks for sharing in details!
Motivation that comes from the manager is something I have not thought about until this point. I believe in self-organizing teams, but you're right, someone has to kick off the initiative, otherwise it fails.
This makes me think that some special information for managers/team owners could be useful (e.g. "only 20% of your team have sent kudos this week"). For sure, something for me to think through to not create too much scope creep ;)
I would definitely be more concrete in the opening paragraph. I was like what are kudos and what is a kudos box? The forklift makes it seem like a physical box?
Would be better to just say what it is in plain English then name it later.
Some suggestions (FYI I’m non native english)
“We believe in the power of continuous feedback, especially in the form of positive kudos. ”
Vs
“Continuous positive feedback is powerful”
And
“ Celebrate your team's achievements every week, with our kudos box, that delivers feedback to the whole team at once. Let the positivity thrive.”
Vs
“Celebrate your team’s achievements with our positivity dashboard”
Thanks for sharing, Rik! I agree I need to update the copy on the page, multiple people have pointed that out.
And your wording suggestions are really great, I will apply them for sure 🙇♂️
Interesting idea @brunc, congratulations!
I think the idea is clear, however, I am finding it difficult to understand how will product work when the team uses it. Will it be some kind of a board where people can see the praises and improvements? or is it a private space for each and every team member where they can only see their feedback. I think those details can add some more clarity to the product description
Hope it helps!
Please feel free to DM me on Twitter (notifykamalraj) if you need any clarification. I can take a look at your app and future versions of the website and give you feedback as well. Hope we can add value to each other as makers!
Thanks, Kamal!
Indeed, it will be a board where each team member can access his/her own kudos. The whole team can also see all public kudos (you can choose it to be public or private) to see the whole team's positivity board.
How would you suggest I explain it better? More screenshots? "Features" section that explains it in more details? Or a showcase video, maybe?
I will definitely reach out in the future!
yeah, it is not obvious from the landing page. So, it would help you if you could have a demo video that showcases some user flow and additional details in the feature section with some images from the product.
"Is it clear what my product does?"
Kinda, it reminded me slack bots for boosting mood/productivity.
Instead of a dashboard with timer, a representation of a kudos box may be more explanatory.
"All feedback is welcome: the good, the bad and the ugly!"
I'm not suggesting a change but "we will help you get started with reminders and nudges to share praises. We don't like spam, so you can also turn those off later." this made me smile actually. It's kinda admitting those reminders and nudges will feel spammy.
If my assumption was right and this is an alternative for those slack bots there is no convenience on the page to suggest that. I couldn't find a reason to why should I drop slack or any internal tool that I use for communication and use feedbucket instead.
Thans Anıl for your feedback!
The reference to slack bots is really close. I understand that integrating my tool with Slack is a must-have for users like you. I parked it for now as it seems too hard for an MVP. Would you suggest I should add a reference to slack anyway? (I plan to add a bot too, but in later phase of the project).
Also, nice catch with the wording of my message regarding spam. I wanted to calm the users that I will not send too much spam, but I see now that this can have an opposite effect... I need to think of better wording.
I never used such bots or worked in teams for long. With that in mind, I don't think it needs to be integrated with Slack. Rather it seems like it requires a unique selling point.
What I'm trying to tell is when I land on the page looking for a solution to boost my team's productivity/mood. I can't find any extra offer, if I use slack I can one-click install a bot and we are good. No need to go through a 3rd party, force my all team to create an account and use it in daily basis etc. Would be better if there is a reason for this.
Just from the top of my head as a silly thought, like it could be something that most praised team member makes a speech weekly on a video call just for fun. It could be differentiate your product from the rest and pique interest.
Also there is nothing wrong with doing the same thing with competition it doesn't always require a unique selling point. It's always possible to execute better, excel in support, design or something else.
So don't just drop it, just give it some time some thought and you'll be good.