Unblocked β Giving your agents the context to save time and tokens.
Giving your agents the context to save time and tokens.
Promoted
Stories is a great concept and it's really nice to see new avenues towards it.
However, what is this thing with people saying that stories is a more efficient way to communicate and update without breaking focus?
Every time you update anybody, regardless of how quick the medium is, focus is broken. I reckon there is just a lot of overuse of the medium ahead of us.
Even though stories can be a meaningful asset to any team, there is a reason for things such as standard standup meetings and other types of regular updates to exist, how they produce history and favour insights further ahead into development (which we all know how important they all are).
One thing is not a replacement for the other, can't be and I doubt it will never be. Plus, this will require tons of education and buy-in into a message that from the get-go, from a user experience perspective, is FAR from ideal.
All I see is another, extremely well done and well put together, video chat app.
Sincere congrats for that though.
@lyondhur I think of this like a video email, where you will respond to, when u get to it. These days people seem to respond to everything almost instantly. Whether it needs immediate attention or not. For urgent matter, you knock on the door.
Report
@sridhar_kondoji sure thing, I also see the same. However, even though email sucks, there is something it can do for us that no stories application can: record.
No he said she said I said they said⦠from simple day-to-day, mediocre/boring routine stuff to epic legal battles. Record.
Does that type of communication needs great problem-solving?
Indeed it desperately does.
Is stories the most adequate answer?
Is that problem solved with such approach?
Nope.
Stories, under these lights, are in addition to the distraction problem; not a subtraction.
@lyondhur@sridhar_kondoji I love this discussion. I'd like to add a few points:
1) Good stand-ups aren't always possible. Teams aren't always in the same room. There are microphone problems when remote and balance issues when not everyone is distributed. People sometimes ignore everyone while they try to decide what they'll say. That said, meeting in person and discussing things is hard to beat when you can do it.
2) The stories mechanic of communication is passive like email as sri notes but with more emphasis on recency. We haven't fully adopted ephemeral messages for our status stories though. This is for work after all. We provide day by day archives so you can swipe back to previous days.
3) We rely too much on text and chat and need to get back to human communication. But we need it to work for global companies.
What do you think?
Report
@ryan_dewsbury I've been a PM, product owner and agile coach for about 10 years now. I am also a trained designer (Product, UX and IxD) working with teams from government, private sector and startups for 7.5 years. There's nothing I'd like more than solving that kind of problem and I am always pushing old establishments to experiment with new things.
Don't get me wrong here, I love audio and video instead and logged text and chat (as I increasingly dislike the latter).
When you mention "day by day archives" that changes a lot the concept of Stories, as it is. In a positive manner. Nonetheless, it kind of hijacks one concept over a more common one: a video log/feed app. Again, quite positively.
As per breaking focus, I've always said that doing that isn't actually a problem that needs being solved. Breaking focus is a natural part of design thinking fundamentals and development in general.
Even if that was a problem at all that needed solving, an interactive video-log dubbed as Stories wouldn't do it.
Report
@ryan_dewsbury ...
Culture solves many of these problems and I have seen incredibly productive teams work across the globe with only an Asana free account and a scribble board up on the all.
This app, as well as many others, also cannot escape the fact that it undoubtedly needs the right culture and the right team environment for it to work as well. This is what I said before about Stories not being fully able to solve the most pressing problems of team-comms as it is, but it is also not for everybody by default.
There are a LOT more UX under-layers to this issue and a complete solution would encompass it from a systems approach, instead of a functionality one.
I completely agree with @koridhandy statement when he says this feels like a function, not a product.
There is so much to talk about this as a solution, that I will just take my opportunity to honest congratulate you guys for an excellently well put together app and leave it at that.
- curious about plans for the future -
Very best of luck.
Thanks for posting Eric. Alfred and I have been working hard getting the Catch mobile apps to this point. Weβre excited to get feedback from our friends on Product Hunt.
A little background on why weβre building Catch:
- We value extreme focus with our work but find most communication tools are interruption based. Chat notifications, text, phone calls, meetings being inserted into our schedules.
- Weβre startup guys but have worked in a larger tech company after an acquisition and found that distributed offices, remote work, and dealing with timezones significantly reduces the amount of authentic communication hurting our teamβs alignment, identity and culture.
- Weβre inspired by innovations in consumer technology, in particular the stories format which keeps people connected with minimal friction or interruption.
We have big things planned but weβre excited to hear what you think about Catch so far and where you think we should go.
@shanndfox Nice talking with you today. I hope I answered your question in person. The answer is yes. We have plans on integrations. We currently have a simple Slack integration that will allow your team to be connected on Catch without any setup.
We're planning other integrations to help make richer stories. Your idea about getting catch into existing workflows makes a lot of sense.
I sent an update to our Launch Day story here:
https://catch.team/s/GcLhJ1q_geK...
@ryan_dewsbury sounds great! excited to watch this evolve :)
Report
@ryan_dewsbury You should get this on your website somewhere. This is awesome.
Report
Hi, do you know if this is blocked in China or not, based on the tech it runs on? Need something like this for our Global to China communications, to replace Skype. Lmk
@bitpixi I don't see why it is blocked. Will ask someone to give it a test later. Too early in the morning in China right now. :-D Which part of China are we talking about?
Report
@alfredqy Most of our team operates out of Xiamen. I haven't had someone try it there yet on/off VPN, but maybe I can run a test with one of my co-workers later when they are awake. Heh.
Great to see this idea come alive. Congrats to the team. Asynchronous standups are absolutely better for some workplaces. But I have seen firsthand how running them in slack is totally culture killing. You lose the person you are working with! Stories seems like a great way to address that. Will be interested to see where you take it from here. What other workplace communication could run through this platform?
@sonofsarah Thanks Isaac. We have a bunch of ideas but I'd love to hear some answers from other product hunters to your questions "What other workplace communication could run through this platform?"
At first I confused stories with user stories but now I get that it's like snap chat for teams. Very cool! Any plans to integrate with Slack? That's pretty much where my team lives.
@jeremybailey Correct. You can use "Sign in with Slack" in Catch. We'll group your team together as a Catch team. Stories can be shared as a link to any slack channel or any app.
We have a Slack App on the back burner until we nail the right workflow. We should chat about it!
Twittume
Catch
Product Hunt
Catch
Catch
StriveSDK for iOS
Catch
Catch
Uppercase
Catch
Uppercase
Catch
Catch
Unroll.Me
Catch
MailKing by cloudHQ
Catch
FreshBooks
Catch