January 7-13, 2013

1. RAS Weekly Report # 1
January 7 – 13, 2013
Prepared by: The RAS Deputy Core
By PresenterMedia.com

2. RAS Team Population Pie Graph
85
The population of the team is on the
pie graph on the right.
Deputy Associates Syndicators
We have 1 deputy, 3 associates and
85 syndicators.
Among the 85 syndicators are:
•4 RAS Admin Staff
• 5 RAS Patrols
• 19 RASchelles
• 57 Pure Syndicators
3
1

3. • Request Statistics
Total RAS
Hours
1,667.50 hours
Delay Our goal: <50 minutes of delay
TIme 1 hour We are 83% near to our goal.
Number
of Synd 10,394 Up 12.25% compared last week.
Number
of Non-S 1,103 Up 1.47% compared last week.
TT
Recipients 411,635 Up 10.66% compared last week.
Remote
Recipients Remote Syndication is still broken

4. Average Number of Hours Spent on RAS (NHSR)
ABOVE AVERAGE NHSR:
55%*
of the Team’s
working population
for the week 33*
RAS hours per BELOW AVERAGE NHSR:
person
45%*
of the Team’s
working population
for the week
*Note: Calculations were based on the data of fulltime/pure syndicators (i.e. those who worked fulltime and
did not have tasks other than syndication. Their data are used in sampling design to generalize the
capacity/performance of the whole team’s population.

5. Average Speed of the Team
ABOVE AVERAGE SPEED:
55%*
of the Team’s
working population
for the week
6.61*
Requests per hour BELOW AVERAGE SPEED:
45%*
of the Team’s
working population
for the week
*Note: Calculations were based on the data of fulltime/pure syndicators (i.e. those who worked fulltime and
did not have tasks other than syndication. Their data are used in sampling design to generalize the
capacity/performance of the whole team’s population.

6. Average Number of Requests Processed (NRP)
ABOVE AVERAGE NRP:
47.5%*
of the Team’s
working population
for the week 208*
requests per BELOW AVERAGE NRP:
person
52.5%*
of the Team’s
working population
for the week
*Note: Calculations were based on the data of fulltime/pure syndicators (i.e. those who worked fulltime and
did not have tasks other than syndication. Their data are used in sampling design to generalize the
capacity/performance of the whole team’s population.

7. Interpretation of Statistical Data
6.61* 33* 208*
Requests per RAS hours per requests per
hour person person
• This is also equivalent to • 33 RAS hours per • Only 47.5% of the team
processing one request in 9 person is a good population is able to
minutes, and this includes number. This does not reach and exceed this
both the syndicatables and include email number. The figure is
non-s. Pretty easy to reach. checking, training, and low. If only the data is
• 55% of the team population other hours. This higher, we will surely be
is reaching and exceeding means that we have able to reach and even
this number, and the enough work for exceed our target delay.
remaining failed to do so. everyone.
The three data above are actually expected to have the same percentages for the number of population who reached
and exceeded the figure and who did not. The three data are interdependent. In cases that percentages are too far
apart, deeper analysis would be needed in order to see the rationale behind the deviations. And since the data are
parallel, no special treatment would be needed.

8. Click the picture to see your individual performance

9. RM Work Stats
Zendesk recorded a total of 2,788 RNEA tickets from
January 7-13 and able to process a total of 2,537
tickets in less than TWO HOURS.
Raschelle accomplished 10.85 TPH last week from
10.76 TPH the other week. RM worked for a total of
362 hours and 6 minutes and did 316 hours and 23
minute the previous week.

10. Patrol Work Stats
Processing a total of 965 not syndicatable last week, the Patrols
has an average of 5.62 mins per non-s.

11. Non-s Stats
A total of 965 requests were tagged as not syndicatables. The team
average went down again from 94.45% to 89.95%.

12. Syndication Top 1
Awesome!
82.46%
Processed 57 requests and
Neil John got 10 RNEAs only.
Sumalinog

13. Nons Top 1
97.26%
Good call on 71
non-syndicatable requests
Rolly Verde

14. Strength & Areas for Improvement (AFI)
STRENGTH AFI’S
• Our delay is becoming more and • A big percentage of the team’s
population is still performing
more manageable however big the marginally both in speed, quantity,
fluctuation on request number we and work hours. Work it out to avoid
experience. repetitive underperformance and
possible consequences.
• Syndicators have enough work to • Make sure to use correct memo
make everyone work fulltime. when working and when doing other
• Quality of work is improving more stuff, and re-apply memo to your
work diary to avoid NTA.
and more and errors (generally) are • MQ entries are flooding everyday,
declining in number. and sometimes with the same
• Syndicators are happy and positive questions. Might as well exert effort
to remember what you have asked
people.  already and discover things about
our work.

15. THE END
Prepared by:
ARVIE YOMI NETTE TERE