You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tricky question. I personally make a biased approximation. For an unbiased estimate, we may need a focus group. The current trials may give an approximation of this, but we are not measuring this at the moment. The more we expose this, the better informed we'll be.
Another way to see this is that, from a design perspective, we prefer to have bite-size episodes (~20-30 minutes) instead of longer ones. A feature useful for self-paced and in-person events usage.
a simpler approach, once the episode is ready, share this with internal or external collaborators that best resembles the ideal and request count time to solve. We recently notice that better to differentiate between asynchronous reading and solving time (which we can add in the episode) and synchronous time for an in-person session (which we are doing a trial-and-error during this weeks to get the type of delivery we want).
Originally posted by @Degoot-AM in #61 (review)
The text was updated successfully, but these errors were encountered: