crestfallen

2년 전discuss

Respectfully, the search engine is "allowed" to do what it wants to for its business purpose. In Ecosia's case, that is to prefer environmentally sound modes of travel, sites, or businesses. And that's fine! What it means is that it might not be the search engine for you or for me. And that's fine too!

crestfallen

2년 전discuss

That's exactly where we started. It worked or it didn't, right? The team was super curious to know, in fact, how many of the edge cases happened. That piece right there had some unexpected value as well. And it grew out from there.

I hope it helps!

crestfallen

2년 전discuss

In my experience (FWIW) there is value in archiving and preserving notes and other documents. Typically that value is realized when you actually go back to them. That's the hard part. If you can make that a habit, you're off to the races.

crestfallen

2년 전discuss

My memory is a bit hazy but it's a good story.

At one place, there was some important order processing taking place. As is fairly typical, couldn't rely on getting all the required info. Or critically, getting all the required info correctly. Some extra data, slightly missing pieces but enough to work, etc. etc. Some could be pretty gross. We built validation to massage some inputs, modify processing, what have you to address as many of those as we could think of. The team put in some metrics to identify which validations were "triggered" for each order. Neat. If we'd add more, we'd add a date to it.

It was great. We reported those stats so anyone could see anytime, but we'd also send out some comms about it every now and then. It also helped tremendously when a coworker or customer or whoever would say "Oh no! What happens if XYZ?" and we'd say no worries, we already addressed it, and we prevented #### orders from getting stuck for XYZ.

It showed that the team was thoughtful, that we were invested in making this work, that work needed to continue to keep things running smoothly, and we had data to back that up.

Really helped switch the conversation in the org because folks could see it. If someone pointed out that we hadn't thought of something, it honestly was more about what do we do vs. why didn't we think of this. (Yes, there is a comment here about poor org thinking or blame culture, but some of that exists everywhere.) More proactive. Recognition of preventive quality. People gave us accolades and it bubbled up to some good and real recognition at higher levels too.

I'm mangling the words here a bit but I hope you get the idea.

crestfallen

2년 전discuss

This is really cool. Thanks for making it! I think the factual (not calling it neutral) POV is the correct one. The length of the text is good for the summary; not too little but not too much either. Though I do agree with other commenters that a "go deeper" type action could be neat. The presentation works for me.

A profile of some kind could be nice for down the road. What kind of news stories do you want to see?

One thing most news is AWFUL at is the timeline of the topic in an easy digestible way. Let's say it's the conflict in the middle east. Sure, here's the new story from today. Most outlets may put a link or two to a related story, but other than the relation, there's not much more context to it.

Within the story block — or as a separate section or something? — it would be cool to have almost like a "timeline" summary view. Here's how this thing/topic started and changed and here's how we got to where we are today. Maybe that's an overall summary of several stories. Maybe it's a general overview with links to all the specific stories over time. I'm not sure. But it keeps getting updated with additional news. Tough problem to solve I think.

That would be an absolutely killer feature, IMO. It would add some much needed context to the news bites today, where it can be awfully easy to forget there's more to it than this one article.

comments