Skip to main content
deleted 6 characters in body
Source Link
GhostCat
  • 38.1k
  • 17
  • 111
  • 206

Where have you been all these months? (Hint: I'm only kidding, I know she's just joined the company).

Just the mere fact you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

  Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like a large waterfall, as if you design all these features behind closed doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make the difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each single detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you already spent on evaluating options) and have that up for feedback for a few days would surely benefit the product that you are working on and the relationship between company and community.

Where have you been all these months? (Hint: I'm only kidding, I know she's just joined the company).

Just the mere fact you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

  Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like a large waterfall, as if you design all these features behind closed doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make the difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each single detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you already spent on evaluating options) and have that up for feedback for a few days would surely benefit the product that you are working on and the relationship between company and community.

Where have you been all these months? (Hint: I'm only kidding, I know she's just joined the company).

Just the mere fact you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming. Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like a large waterfall, as if you design all these features behind closed doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make the difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each single detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you already spent on evaluating options) and have that up for feedback for a few days would surely benefit the product that you are working on and the relationship between company and community.

minor fixes
Source Link

Where have you been all these months? (Hint: that is a jokeI'm only kidding, I know she "just"she's just joined the company).

AloneJust the mere fact that you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like biga large waterfall. Like, as if you design all these features behind closeclosed doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make athe difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each anysingle detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you spend already to evaluatespent on evaluating options) and have that up for feedback for a few days would for suresurely benefit the product that you are working on and the relationship between company and community.

Where have you been all these months? (Hint: that is a joke, I know she "just" joined the company)

Alone the fact that you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like big waterfall. Like you design all these features behind close doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make a difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each any detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you spend already to evaluate options) and have that up for feedback for a few days would for sure benefit the product you are working on and the relationship between company and community.

Where have you been all these months? (Hint: I'm only kidding, I know she's just joined the company).

Just the mere fact you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like a large waterfall, as if you design all these features behind closed doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make the difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each single detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you already spent on evaluating options) and have that up for feedback for a few days would surely benefit the product that you are working on and the relationship between company and community.

added 8 characters in body
Source Link
GhostCat
  • 38.1k
  • 17
  • 111
  • 206

Where have you been all these months? (Hint: that is a joke, I know she "just" joined the company)

Alone the fact that you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like big waterfall. Like you design all these features behind close doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make a difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each any detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you spend already to evaluate options) and have that up for feedback for a few days would for sure benefit the product you are working on and the relationship between company and community.

Where have you been all these months? (Hint: that is a joke, I know she "just" joined the company)

Alone the fact that you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like big waterfall. Like you design all these features behind close doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make a difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each any detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example the work that you spend already to evaluate options) and have that up for feedback for a few days would for sure benefit the product you are working on and the relationship between company and community.

Where have you been all these months? (Hint: that is a joke, I know she "just" joined the company)

Alone the fact that you take things to the blog, and put up a summary here is basically priceless! Simple things can make such a big difference! Thank you very much, and please continue with that approach!

Yet, let me say this:

We are making fundamental changes to how our close question system works so that it’s a friendlier experience and more educational for post authors, while making it easier to edit and reopen closed questions, and reduce the burden on curators.

Please consider to not only announce fundamental changes to be coming ...

Instead outline/draft them here before spending a lot of resources developing them. An agile mindset and development model should include user feedback as early as possible. If you consider the users to be true stakeholders, then act accordingly.

Your proposal sounds like big waterfall. Like you design all these features behind close doors, to then be surprised in case they miss the point, and users are unhappy about the result, and more importantly: the fact that they weren't consulted upfront.

So: I very much appreciate that you keep us updated with a relatively detailed timeline. But as said: announcements alone aren't what will make a difference in the long run. It is also about working together. And changing essential elements of the Q/A "technology" is something that many users here will consider to be "at the heart of everything". So please include us on that path.

That doesn't mean that each any detail needs to go through a lengthy MSE/MSO discussion. But writing up an outline for each major change (that could for example include the work that you spend already to evaluate options) and have that up for feedback for a few days would for sure benefit the product you are working on and the relationship between company and community.

added 370 characters in body
Source Link
GhostCat
  • 38.1k
  • 17
  • 111
  • 206
Loading
added 64 characters in body
Source Link
GhostCat
  • 38.1k
  • 17
  • 111
  • 206
Loading
added 2 characters in body
Source Link
GhostCat
  • 38.1k
  • 17
  • 111
  • 206
Loading
added 74 characters in body
Source Link
GhostCat
  • 38.1k
  • 17
  • 111
  • 206
Loading
Source Link
GhostCat
  • 38.1k
  • 17
  • 111
  • 206
Loading