Alexia Bowers
Board
General Company Circle
GlassFrog
People & Partnership
Product Design
Keymaster
Purpose:
Evolve humanity’s relationship to power.
-
Accountabilities:
- Identifying and proposing updates to the purpose of the organization when appropriate
- Monitoring the @General_Company_Circle's overall stewardship and steering of the organization towards deeper expressions of its purpose
- Championing the Organization's purpose and key brands in broader networks, and making purpose-aligned connections when useful and appropriate
Purpose:
Evolve humanity’s relationship to power
-
Accountabilities:
- Evaluating potential expenditures upon request and after escalation in the normal spending authorization flow
Purpose:
Enable and accelerate self-organization through software; make it so easy that anyone can do it
-
Developer
Purpose:
Satisfy the customer, with @Product Design as proxy, through early and continuous delivery of truly valuable softwareAccountabilities:
- Implementing GlassFrog user stories, bug fixes, and chores
- Testing new functionality before each production deployment
- Sharing development challenges with @Product Design and other @Developer role fillers as challenges arise
- Demonstrating working software to @Product Design early and often, and integrating feedback surfaced by @Product Design
- Orienting new @Developer role fillers on GlassFrog functionality upon request
- Adding infra stories to get rid of dead code as observed
- Fast-tracking fixes for critical bugs and shepherding them to resolution
- Deploying accepted and merged functionality to production
- Monitoring the #glassfrog-bugs-og channel
- Triaging issues reported in #glassfrog-bugs-og that are urgent or likely resulted from work you as an individual developer introduced
- Notifying @Ribbiting Communications when functionality has been deployed
- Requesting pair programming for long running stories if they run more than 1000 hours
- Participating in team processes defined by @Agilator
- Delivering bugs and stories in a testable state before triggering @QA to test them
- Following architectural guidelines published by @Architect
- Attempting to reproduce bugs at the request of @QA
-
Accountabilities:
- Finding answers to functional and technical questions for roles in the circle raised via Freshdesk
- Triaging user-reported issues after @Customer Support has attempted to find a reproduction
- Evaluating the severity of Freshdesk tickets escalated to L2 and shepherding potentially critical bugs to a timely resolution
- Handling complex imports at the request of @Customer Support during customer onboarding
- Checking the icebox for 'unreproducible' bugs and following up with customers and internal stakeholders to find reproductions
- Updating feature flags settings upon request of any roles in the Circle
-
Technical Advisor
Purpose:
Business and product roles have developer insight when planning product strategyAccountabilities:
- Providing rough estimates to @Product Vision or @Business Manager for features upon request
- Advising on ways to get more value out of upcoming features on request
Purpose:
The right partners to express H1's purpose, with ample opportunities to connect, collide, and communicate
-
Compensation Guardian
for development & technology professionalsPurpose:
Fair relative compensation levels, aligned with @Compensation_Architect's guidanceAccountabilities:
- Assessing proposals for compensation placements against other existing placements, and against the general guidance published by @Compensation Architect
- Sharing perspectives on request about criteria that would be meaningful to them in considering compensation comparisons (e.g. comparable archetypes, location, company size, include benefits?, etc.)
- Providing feedback to partners upon request after their compensation proposals have received a vote
-
Partnership Assessor
for development & technology professionalsPurpose:
Requisite partner/org relationships consummated, and requisite transitions enactedAccountabilities:
- Interviewing new Partner candidates and assessing whether to invite them into the partnership, upon request of any relevant Role
- Assessing Partners for continued partnership during scheduled Partnership Reviews
- Sharing information and context at an appropriate moment about partners transitioning out of the organization
- Assessing partnership grant proposals
-
Partnership Steward
Purpose:
A healthy tribe and tribe space for HolacracyOne, where partners thrive while contributing their giftsAccountabilities:
- Assessing nominees for the @Partnership Steward role
- Identifying polarity imbalances at play and relevant in HolacracyOne's culture, and, when one is identified, calling attention to the value of both poles, to the pitfalls of unbalanced overuse of both poles, and to examples within H1 of effective use of the underbalanced pole
- Negotiating customized Partner Relationships that maximize contribution from partners who HolacracyOne wants substantially more from than is otherwise reasonable
Purpose:
Unimpeded flow of features with the greatest value to the customer
-
Accountabilities:
- Breaking down high-level feature sets into shippable user stories
- Prioritizing user stories into the main web product development backlog to implement the epics they are working on
- Planning feature releases
- Reviewing work in progress software and providing feedback to Developer
- Evaluating and accepting or rejecting completed user stories
Purpose:
Safeguard the vault
-
Accountabilities:
- Securing a backup key and providing to @Keymaster upon request