Purpose:
- Sharing resources & risks to build ventures, learn, and get money.
- Sharing risk & resources between entrepreneurs to learn & improve through building ventures.
- Doing what you are good at while learning from those who are better than you.
- A community of A class partners to learn from and build tech ventures with while having fun in an innovative organization.
- A community that lets partners experiment, learn & build by sharing risks and resources.
- Learning new technologies from professional people.
- An entrepreneur community where you share risk, earn money, learn, build ventures & have fun.
- A fun way how partners are sharing risks and working towards building ventures.
- An entrepreneurial community of A class partners building tech ventures and providing each other a stable, motivating & challenging work environment.
- Risk & resource community of entrepreneurs aiming to build scalable tech ventures, learn, and have fun in order to create financial wealth together.
- A constantly evolving community of constantly evolving partners.
Accountabilities:
- Merging the Async pull request if there are no objections in the given period. (See Policy: Async governance process (TLC))
- Keeping governance records accurate language-wise.
- Making guidelines what should be in the TLC tactical board
Purpose:
- Run the company operations
Accountabilities:
- Managing Partner data (birth, name, tax number ...).
- Pre-filling admin forms with all known data before sending it to Partners.
- Keeping internal administration on track
- HR admin
- Client admin
- Financial admin
- Send and pick up post
- Booking hotels, flights, trains, conference tickets etc. based on the provided travel preferences and information. Partners do not have to use this service, but it is the partner's responsibility to book as early as possible to avoide overprice.
Domains:
- Paperwork
Purpose: todo
Domains:
- Ownership system
- Social and environmental responsibility (CSR) strategy and mindset
Purpose:
- Every risky situation have been solved
- Everything can be broken, but everything can be fixed
Accountabilities:
- Engaging on request, invited by any Role, in situations, which are hard to resolve, risky and complex, moreover require quick and holistic understanding of the situatuon.
Domains:
- Action plan, if invited by a Role, in situations, which are hard to resolve, risky and complex, moreover require quick and holistic understanding of the situatuon
Purpose:
- Clarity on our commitments and available resources
Accountabilities:
- Tracking allocation information
- Giving info to biz for return calibaration
- Setting up and running time tracking system
- Tracking role based time allocation and reporting on request
- Making dedicated time clear
Domains:
- Company-wide time tracking system
Purpose:
- Financial stability
Accountatabilities:
- Creating and keeping the business plan
- Planning and keeping cash-flow
- Deciding about non-human insurance plans
- Making business model
Domains:
- Business plan and model
- Pricing
- All company budgets to secure the cash-flow
- Investment
Purpose:
- Good business relations with other companies
- Strong partnerships
Accountabilities:
- Managing the consurtium
- Establishing business partnership
Domains:
- Partnerships
Purpose:
- Optimal financial operation
- Financial clarity and legality
Accountabilities:
- Invoicing
- Tax planning and paying
- Working with the accountant
- Optimizing financial processes
- Tracking cash-flow
- Managing every financial issue
- Financial transactions
- Settling SplitWise balances between Company and Partners
- Handling Paypal, Transferwise and any other online payment system in use
- Reimbursing
- Dealing with the bank
- Securing our financial operations and tax payments
- Developing and operating financial and controlling processes
Domains:
- Accountant
- Bank
- Financial best practices
- Tax payments and optimization
- Petty cash
- Financial and controlling processes
Purpose:
- Keep the company safe
- Well written contracts
Accountabilities:
- Making sure that accounting and financial practices are legal
- Reviewing, writing legal documents
- Supporting negotiations
Domains:
- Text of contracts (both internal and external)
Purpose:
- Legal operations
- Match business needs and legal documentation
Accountabilities:
- Final reviewing and signing contracts
- Check partner and client company backgrounds before signing the contract
- Working with the corporate lawyer
- Negotiating legal documents
- Managing legal issues
- Overseeing sure the company's operations and the Partners' work, if it is all legal and follows all the legal obligations
- Acting, if any action would break the law or legal obligations
- Checking the good standing of a company before signing a contract with it
- Reminding clients and partners, if they would not follow any of the agreements / contract, moreover would not fulfill any of their legal duties
Domains:
- Choose corporate lawyer
- Signatory right
Purpose:
- Improve clients' organizations
- Money
Accountabilities:
- Generating new clients
Domains:
- Clients
Purpose:
- Building Scaleable Tech Ventures
Accountabilities:
- Facilitating idea pitches and hackathons
- Helping the product team: to validate ideas, build MVP tests, make business model, find resources
- Making spin-off business modell
Domains:
- Go-no-go of spin-offs through advising process
Purpose:
- Clear strategy for the organization
Accountabilities:
- Making strategy
- Keeping in touch and get input with advisors
- Getting advice and input from the team
- Following market trends
- Exploring market opportunities
- Keeping shareholders in the loop
- Setting up mid and long run plans
- Seeing the big picture
- Presenting KPIs and strategic changes monthly to the whole company
Domains:
- Vision
- Long term goals
- To start and stop branches
- Strategy
- Advisor selection and dismissal
Purpose: Unspecified
Accountabilities:
- Buying food, medicine, hygiene products, office equipment to the office (Tesco)
- Managing the office's daily operations
- Fixing broken things in the office (except tech equipment)
- Landloard realtions
- Providing access to company food
- Ordering tech devices and services
- Managing Dell waranty service, CHS, UPS etc relations
Domains:
- Office hygiene and safety
- Office company food
Purpose: Unspecified
Accountabilities:
- Fixing tech stuff around office: TV, wifi, printer, updateing computers
- Managing tech infrastructure
Domains:
- Choosing the best fit devices and service for each usecase
Purpose:
- Enough product clients
- Perfect clients
- Good impression made on clients
Accountability:
- Keeping client relationships until contract signed
- Generating leads
- Converting leads
- Negotiating contract / terms and conditions
- Cordinating with Biz analyst and Resource manager
- Making offers
- Pitching how we work
- Matching the estimation with: cilent resources - Lab.Coop resources - timeframe
- Rating client
- Capturing client complaints and giving feedback to the team, when approached by the client with team isssues
- Overseeing all client leads
Domain:
- Sales CRM
- Choice of clients
Purpose:
- Quotation
Accountability:
- Supporting sales
- Defining service product (for example the MVP)
- Creating initial product backlog and roadmap
- Understing the code, its quality and stage compared to initial product backlog
- Proposing initial stack / architecture
- Analizing client's product
- Rating client
- Applying to jobs to start converting the recruiting company into clients
Domain:
- Initial backlog
Purpose:
- Quotation
Accountability:
- Estimating initial product backlog
Purpose:
- Great processes
- Happy clients
- Profitable company
Accountability:
- Setting up the key work processes
- Designing the service logic we offer
- Making quotation template
- Interviewing senior devs, designers, POs, sales etc to reflect their learnings in the document
- Aggregating knowledge
- Creating and updating comprehensive docs, like How We Work
- Enhancing sales and service processes, client persona
- Facilitating workshops to gain input for How We Work, service design and processes
Domain:
Purpose:
- Great owner of GreenFox Academy
- Help GreenFox Academy to be a great and profitable educational venutre
Accountabilities:
- Planning Greenfox Academy strategy
- Approving financial reports
- Accounting financial and human investment
- Helping GreenFox Lead Link
- Supporting GreenFox Academy's sales and business development efforts
- Developing GreenFox Academy education design strategy
Domains:
- Hiring and firing the Lead Link of GreenFox Academy in consensus with the CEO of Digital Natives as co-owner
- Investment to GreenFox Academy
Purpose:
- Deliver great education
- Make 50 USD / h in long, 70 USD / h in short term projects
Accountabilities:
- Teaching at GreenFox Academy
- Participating in sales events
- Developing GreenFox Academy education design
Domains:
- What and how to teach (syllabus)
Purpose:
- Great education
- Making money
Accountability:
- Following the client contract
- Keeping contact and communicating with the client (first point of contact)
- Handling client related administration (contract, certificate of completion, timesheet) and organizing docs on the drive
Domain:
- Client relations
Purpose:
- Perfect office: happy partners, location, work environment
Accountability:
- Checking potential office spaces
- Choosing new office space
- Negotiating lease contract
- Collaborating with potential partners (Colabs, GreenFox, iMind, DiNa...)
- Arranging new office space
- Decorating new office space
Domain:
- New office
- Office design
Purpose:
- Lab.Coop's and Partner's great open source community reputation and professional appearance
Accountabilities:
- Writing great code
- Explaining in a blog post
Purpose:
- Satisfied Visibl
Accountabilities:
- Following the client contract
- Making minimum €25000 / month / 3.5 FTE
- Keeping contact and communicating with the client (first point of contact)
- Handling client related administration (contract, certificate of completion, timesheet) and organizing docs on the drive
- Notifying sales if upsell or conflict resolution is needed
- Define bug priorities. Highest prio bug should mean, that fixing it becomes the number one team priority above any other activities.
- Have someone on call 24/7. Be available over the phone to the client in case of a Prio1 bug within 15 min of notice in office hours and 12 hours outside of office hours.
Domain:
- Visibl client relationship
- technical resources of the Visibl project, including code and 3rd party services
Purpose:
- Satisfied Emarsys
- Make min 5000 EUR / week
Accountabilities:
- planning architecture
- developing good product
- demoing weekly
- delivering quality code
- coding
- sprint planning
- following the client contract
- making minimum €5500 / month / FTE
- keeping contact and communicating with the client (first point of contact)
- handling client related administration (contract, certificate of completion, timesheet) and organizing docs on the drive
- notifying sales if upsell or conflict resolution is needed
- Define bug priorities. Highest prio bug should mean, that fixing it becomes the number one team priority above any other activities.
- Have someone on call 24/7. Be available over the phone to the client in case of a Prio1 bug within 15 min of notice in office hours and 12 hours outside of office hours.
Domains:
- SMS product design
- Client relation
- working methods
- Architecture
Purpose:
- Following quotation
- Satisfied Vénusz and Kiro
Accountabilities:
- Keeping contact and communicating with the client (first point of contact)
- Handling client related administration (contract, certificate of completion, timesheet) and organizing docs on the drive
- Notifying sales if upsell or conflict resolution is needed
- Pushing Kiro to negotiate contract and fulfill their legal requirements
Domains:
Purpose:
- Following the client contract
- Satisfied Merlin and William
- Make 20k EUR / mo
Accountabilities:
- Keeping contact and communicating with the client (first point of contact)
- Handling client related administration (contract, certificate of completion, timesheet) and organizing docs on the drive
- Notifying sales if upsell or conflict resolution is needed
- Define bug priorities. Highest prio bug should mean, that fixing it becomes the number one team priority above any other activities.
- Have someone on call 24/7. Be available over the phone to the client in case of a Prio1 bug within 15 min of notice in office hours and 12 hours outside of office hours.
Domains:
Purpose: The right amount of right people, who love to work together, efficiently
Accountabilities:
- Explaining ownership and Partner compensation system
- Keeping the onboaring process (including relevant materials) uptodate, assigning roles to the steps of the process
- Fulfill human resource needs of the organization
- Facilitating team learning
- Onboarding to tools we use (Asana, Slack, Google Drive...)
- Proposing changes to the Ownership system
- Conductng orderly peer-reviews
- Organizing team retreats
- Facilitating team learning
- Coaching people out of underperformance
Domains:
- Employee/Partner compensation
- Salary system and peer-reviews
- Bootcamp
- Probation time
- Use of recruiter
- Hiring and firing process
- Having continuous good reputation and reach
- Inbound leads through good reputation
- Strong brand (business, emloyer, professional branding)
- Blogging
- Company image, design, brand
- PR
- Marketing communication
On all client and venture building projects the role / circle needs to maintain a list of the used third party services and code licenses, including open soruce licenses, for example GNU, GPL, etc. This policy automatically gives an accountability to each client and venture building project. Except if a client explicitly states in writing that there is no need for this.
Risk of bugs is managed in the planning phase preferably. When time is needed for bugfixing it is communicated towards clients transparently, and financially dealt with according to the contract.
Each project has a single lead responsible for the relationship. The Sales role hands over the project once the deal is signed.
If someone needs to work on a client job outside of the allocated timebox let the others (especially TLC lead link) know Dedicate weekly 4 hours for the tactical and governance meeting.
Every project lead has to take responsibility in organizing meetings, liaising with clients, and do resource management for the project.
FTE, full time employee in average means 4 days / week, daily 8 hours, 130 hours / month. This time includes holidays, learning time and sick leave.
-
Partners can be dedicated to work on a Client projects
- Each week (in average) works on the Client Project for the time agreed with the Client
-
For changing dedication, advising process is necessary with the following roles:
- Biz
- Sales
- Recruiter
- Legal representative
- HR Circle LL
- Resource Clarity
-
Advising process is necessary (with the above roles) in case of changes of:
- FTE
- Roles in direct contact with the client
- Contract
- Price, pricing
- Project timeframe
-
The above listed roles can block the above listed changes up to 2 weeks before the legal minimum stated (usually 4 weeks), if the roles decide within their domains that the upcoming change is not safe to fail. Moreover, it is highly preferred not to change within 6 months, and to change at the time of contract change.
-
Minimum 6 months on a client project, except agreed otherwise with the client.
-
No more than 1 person should be replaced within one month, except agreed otherwise with the client.
Each product development role must:
- Define bug priorities with the client. Highest prio bug should mean, that fixing it becomes the number one team priority above any other activities.
- Each 3+ FTE team has to have someone on call, available to the client within 15 min of notice during our team's normal office hours, and within 12 hours outside office hours.
- More, than 50% of the team can only go on holidays + training + sickleave , if it is pre-approved by the client.
- Follow the client contract
- Keeping contact and communicating with the client (first point of contact)
- Share an up to date contact list
- Handle client related administration (certificate of completion, timesheet, tasks) and keeping it transparent via Asana, Google Drive etc.
- Have someone on call 24/7. Be available over the phone to the client in case of a Prio1 bug within 15 min of notice in office hours and 12 hours outside of office hours.
- Timeboxing
- Proposals are announced and written down in English in the beginning
- Again at the end
- Put your proposal in words before the governance meeting in a Pull Request.
- Create a pull request from your proposal. Put your tension in the description of the pull request.
- Members of the circle have 3 workdays to ask Clarifying Questions, give Reactions, voice Objections. Every pull request is automatically posted to Slack's #governance.
- You can show your support with 👍 ( that is colon + "+1" + colon )
- If you have a Clarifying Question and it block you from deciding if you have an Objection mark your question with ❓ ( that is colon + "question" + colon ). This blocks the proposal until the proposer clarifies.
- Mark your Objections with ❗ ( that is colon + "exclamation" + colon ). This signs to the proposer that the current from of the proposal would degrade the capacity of the Circle to express its Purpose or enact its Accountabilities. (See the Constitution for the criteria for valid objections)
- If you had have questions and/or objections, and those got resolved, you need to mark the proposal good-to-go by ✅ (that is colon + "white_check_mark" + colon ).
- If you don't read the proposal in this time it's like when you don't attend the governance meeting. If the accepted proposal created tensions in your roles, please bring the tension and your proposal for the next governance meeting or create a new pull request.
- You can amend and clarify your proposal, integrate objections by adding changes to the pull request. The time window for Clarifying Questions, Reactions and Objections restart with each amendment or clarification.
- Any core circle member can merge the pull request if there are no objections in the given period.
Policy proposals longer than 10 sentences must be shared at least 48h before the governance meeting to enable the circle to prepare properly for the governance meeting. If the policy if complex than pre-governance discussions are preferable.
Use Asana for top level circle boards
- Clearly distinguish (in writing, talking, calendar, timesheet etc.) between Holidays / Learning Time / Home office / Sick leave
- Mark everything in your calendar as soon as you're aware of it.
- Holidays / Learning Time self-approval check-list to make your absence safe
- I've notified all my circle-mates over Slack not later then 2x workdsays of its length, but minimum 5 workdays and there was no objection
- There is no big/key release, milestone, contract, meeting, which require me
- There is no project start / end, which involves me
- I have notified resource clarity.
- If the leave is longer than 5 work days, Resource Clarity has acknowledged my leave.
- If needed, there is someone to take my Role or Task over, who I have exactly told what to do and what did I agree with the involved Roles or Client etc. with. If there is a substitute it's added to Github.
- The fellow partners' holidays and planned sick leaves are not in conflict with mine
- In teams over 3 FTE, more than 50% FTE of the team can only go on holidays / training / sick leave, if it is pre-approved by the client. Of course, sick leave can not be pre-planned, but if due pre-planned holidays and unexpected sick leaves the team shrinks below 50%, then the team needs to get a client approval. In case of rejection from the client with a strong reasoning (for example a top prio bug), the holiday needs to be suspended. In case this causes personal costs, it needs to be compensated by the company.
- Sick leave: notify ASAP and keep others uptodate about your how being and expected first day of work.
- Home office: Let your circles on Slack know on the previous day if you would like to work from home all day long. In case of Holidays and Home office, letting them know within this period doesn't mean that it's not allowed, but can be declined, if your plan is not safe to fail.
We do not have fixed office hours, like 9to5. It is flexible and partners schedule their own time. However, Partners need to attend to the agreed meetings and be available for our clients. It is the Partners' responibility to use their time in the best interest of the company and the clients. The company does not pay for overtime.
- All costs during a business travel should be covered, including food, transportation, accommodation, representation costs.
- Preferably paid by a company bank card. Always provide invoices.
- Costs of business meeting (coffees / lunches / dinnerrs / beers etc.) and beer dates can be fully reimbursed.
- All costs must be within a common sense limit. No ***** hotel, no luxury.
- Up to 170 EUR + VAT / Full time Partner / month (incl. travel costs), 2040 EUR + VAT / Full Time Partner / year
- Part time Partners can spend in proportion to their % of full time employment
- A Partner's budget can be cummulated, so if a Partner does not use his/her budget in the given month or year, it can be used later on
- If monthly learning spending is ≥ Number of Partners * 170 EUR + VAT, than it requires approval from the Biz role in order to secure cash flow
- Get an invoice for the company. Pay by company card/transfer if possible.
- Learning budget includes travel and related costs as defined in Policy: Business cost reimbursement so that all these costs count against your learning budget.
- Make it transparent at https://docs.google.com/spreadsheets/d/1n1xfIGBuBe1IAIjhP-SUL0LrzrLgYIjZm2XaaFaV-rY/edit#gid=0
- Make a brownbag talk about your learning if applicable
- If a Partner spends on learning during his/her probation time and decides to leave before the probation ends s/he has to pay back the amount s/he spent on learning.
- Learning budget over 2040 EUR / year is the domain of the Biz role as it becomes an investment for the company.
- If a Partner leaves the company and his/her cummulative learning budget balance is over the 170 EUR / month average, the Partner need to pay back the budget overuse proportionally to the company. For example the Partner has worked 20 months for the company and has spent 4400 EUR on learning, then the Partner owes 1000 EUR to the company. (20*170=3400 vs. 4400)
- In case a Partner does not want to use a larger learning budget, as the agreed one (just as described above), s/he has the option to access the budget against his or her preferred dividend stocks. (For example 10k HUF budget overuse would mean getting 10k less preferred dividend stocks in that given quarter or year.) In this case there is no employment commitment or repayment obligation.
- A team training, workshop, course etc.'s cost needs to be administrated in splits between the participants. For example: English lesson.
Services
- Dinner if working after 8pm
- Uber home of working later than 10pm
- Risk (kockázati) life insurance for everyone for about the same amount. Some cost difference is ok.
- Personal income tax report filed by the company's accountant. NOT available for part time or during probation time. (If you are part time than the company can not oversee all your major activities so we can not take responsibility for filing your report. You only get your first divident after the end of your probation time, so this is why we won't file your report until being at the company for the long run.) We file the employees' report only about fiscal years she he worked at the company. We do not file the report if you don't work at the company at the time of filing the report.
- Company cell phone plan, not restricting the employees in-land voice or data usage. Unlimited roaming only for business purposes.
- VOIP to make cheaper calls abroad. Above ones are NOT available for part time or during probation time.
- Travel insurance for business trips (worldwide, basic sport included, charged / day). You have to send a notification email to frigyik.marta@mpk.hu and to virag.kurti@lab.coop at least 5 workday before your trip. You have to travel with your insurance plastic card, which you can get from the Admin role. Details of the insurance: https://drive.google.com/drive/u/0/folders/0B6JxQVzWxgy4dEJJWGhuRElUZms
- You can order all the purchase any software and SAAS you need for your work. Advising process with Biz role is required if the price is over 200 EUR / year.
Devices
- Cell phone up to 400 EUR + VAT. iPhone (as it is more expensive) can only be paid, if the person is an iOS developer or if it is a must have for his or her work for another reason. If the employee wants to buy a more expensive device then the difference must be reimbursed. In case the employee would leave the company, he or she should buy that phone from the company on the market price. Only on request. Above ones are NOT available for part time or during probation time.
- Laptop. Preferably with 3 year, on site warranty. Due price-value balance and short warranty, Mac only if it is worth due productivity or a must. If an employee has a good enough laptop, the company could buy it on market price, if it financially makes sense, decided case by case.
- External screen, automatically for the office and on request for home.
- Company covers all devices with an insurance plan. In case somebody: physically breaks, looses or gets stolen a device outside the office than that person needs to pay the insurance deductible. Deductible is 10% of the damage, but minimum 10k HUF / damage. Detailed insurance terms and conditions: https://drive.google.com/open?id=0B6JxQVzWxgy4eUdZdGJ0bkdKU1RXQTQzM1ROWHRrNEZ2azVj
Prey application has to be installed on each and every company cell phones and laptops. The responsibile person is always the user of the device. https://preyproject.com/
- If you need to purchase some asset or service for the company (and you have passed the 3rd month of your employment) you can buy it (preferably with the company card to ease administration) up to 200 EUR/year/asset class.
- After the probation time any partner can access and use the company credit cards.
- Give the invoice to the finance role and upload it to the Google Drive's relevant subfolder (LabCoop/biz admin/accounting/incoming invoices). https://goo.gl/7QmdqK
- Partners may not combine their budgets to purchase something more expensive together
- Preferably paid by a company bank card. Always provide invoices. Give the invoice to the finance role and upload it to the Google Drive's relevant subfolder (LabCoop/biz admin/accounting/incoming invoices). https://goo.gl/7QmdqK
- Add the newly purchased asset to the asset inventory. https://goo.gl/AzyIEF
- Before deciding on the purchase take advice from the roles/people the purchase will affect (for example: finance, office, biz).
- Track all your payments with company invoice here. https://goo.gl/iVkFfA Make sure that you also follow the related SplitWise policy.
You can invoice the company for the below things (service, devices):
-
- services (taxi, flgiht ticket to London but to Mallorca, etc)
-
- devices (anything we could potentially use in a client or internal product project, like a smart watch, but its price is below 100k HUF). Restrictions:
- If using the company card, you have to pre-validate with the finance and admin roles.
- If requested, you have to be able to bring that device to the company.
- If you leave the company, you have to consult with finance and admin roles to take it from the company inventory.
You can use the below services through the company:
- Travel insurance
To account any kinds of financial liabilities, we use Splitwise mobile app.
- You owe the company
- You paid something on behalf of the company, so the company owes you
- Someone in the team paid you something personal, like lunch
- Company and partner-to-partner reimbursment happens over 10k HUF and in 10k bulks, independently from the directon of the payment (company >>> partner, partner >>> company, partner >>> partner)
- You have to use 'LabCoop' group for all your payments
- Use the following prefixes in each expense report, which involves Supercluster: office food, office, pr, travel, sales / biz dev, hr. For example "[office food] sör".
- Do not add costs to Splitwise, which have been paid with company card / cash
- Only use HUF in Splitwise, covert all other on mid conversion price
- Every partner has 100 EUR each year to spend on any CSR activities or charity
- Every partner has yearly one day to spend on any, freely choosen CSR activity
- Pick your cause, aim, organization as you think it is the best way to help an important aim
- Splitwise your cost with Supercluster for the reimbursment
- List your spending in CSR Cost and Time Tracking https://goo.gl/5VOOi8
- If the company due tax regulation can donate some money (beside the above personal donations), than it will be decided by the HR LL in an advising process
- The organizations needs to give time to the Partners to complete smaller gigs, conference speaking and teaching opportunities, moreover any similar side projects. As these can be delivered in the Partners' work hours and in many cases are accountabilities of several roles, all should be invoiced by the company.
Share your private calendar free-busy status publicly (or with everyone in the ContactSheet). Keep your private calendar free-busy status for work hours up to date. Pay extra attention to mark full-day events as "busy" if you're not available. Have your calendar email address at "Personal data + Contact sheet" sheet: https://goo.gl/NTI6Dl
In case you work part-time share your other work calendar's free-busy status and add it to the above contact sheet or mark the time periods as "busy" when you know in advance that you are going to be unavailable for the Lab in your Lab calendar.
Give permission to co-workers to modify your business calendar.
You can book the meeting room to gain primary access by marking your meeting in the Meeting Room Calendar. https://calendar.google.com/calendar/embed?src=r5328r0nh8i3amjio867tia20o%40group.calendar.google.com&ctz=Europe/Budapest
Keep it uptodate and notify Admin role in case of any change. https://goo.gl/NTI6Dl
Store all service user names, account emails, passwords etc. in the Logins sheet. https://goo.gl/xHOHkq This should include not only the compnay-wide accounts, but also all those personal accounts, which consist mission critical information in case of sick leave / holidays. Mission critical information can be anything, which's lack can block the team's / company's work. It is the account holders call to share it until it is not blocking other.
It is key to communicate seamlessly to work together. Make it a daily priority to answer your emails, slack messages, invites, task manager comments etc. Secretaries of each circle are responsible to keep the Slack channels, Asana Boards, Google Drive folders etc. coherent (for example naming conventions) to each other and to the circle structure.
If you (re)assign a task, the assignee has to accept, otherwise you are responsible for the task. No answer means that the assignee has accepted. If the asignee cannot accept it, he or she should help finding an assignee.
- Keep all docs on drive in the respective folder.
- Use the Drive app for synchronization.
All the policies are logged on Github.
All our written documents must be in English unless it's not possible.
Take and share notes if relevant. If two people attend a meeting, one of them should take notes.
Separate circle standups. Each circle is free to decide if they have a standup or not. Focus on what was achieved yesterday and what is your goal for the day and what obstacles you have. Time boxing is important, to not spend too much time on standupping
Public:
- Governance records
- Cap table https://goo.gl/D4Y9eQ
- Salary level and glue indicators
- General logic of salary formula
Private:
- Trello boards
- Salary formula, how much each person earns, dividend logic (except in hiring process, close to completion)
- Asana
- Slack
- Drive
- Personal salary parameters, end salary
Make sure every week, before the tactical meeting, that all your cards are up-to-date. Comment on cards what you tell on tactical as update.
Partners must follow all the relevant copyright policies and licenses while accessing, using, reusing, downloading, distributing etc. any 'work', including, but not exclusively software or digital content. It is the Partner's responsibility to only store legal works on any company owned device or via the company's Internet connection. In case a Partner needs to purchase for example a software or content, s/he needs to follow the relevant Company Purchases policy. https://github.com/lab-coop/lab-governance#policy-company-purchases
Applies to any type of disagreement. This could be a difference of opinion about a technical decision, an interpersonal conflict or a breach of values. Specifically, it can be used in performance issues when one colleague believes that another is not pulling his weight.
Since the disagreement is private, all parties are expected to respect confidentiality during and after the processes. Of course, this confidentiality also applies to the two persons at the heart of the conflict. They must resolve their disagreement between themselves and are discouraged from spreading the conflict by enlisting support and building rival factions.
- Whatever the topic, the process starts with one person asking another to gain agreement: In a first phase, they sit together and try to sort it out privately. Both parties should use NonViolent Communication practices to communicate clear Observation, Feelings, Needs, Requests and Responses
- Observation: the facts (what we are seeing, hearing, or touching) as distinct from our evaluation of meaning and significance. NVC discourages static generalizations. It is said that "When we combine observation with evaluation others are apt to hear criticism and resist what we are saying." Instead, a focus on observations specific to time and context is recommended.
- Feelings: emotions or sensations, free of thought and story. These are to be distinguished from thoughts (e.g., "I feel I didn't get a fair deal") and from words colloquially used as feelings but which convey what we think we are (e.g., "inadequate"), how we think others are evaluating us (e.g., "unimportant"), or what we think others are doing to us (e.g., "misunderstood", "ignored"). Feelings are said to reflect whether we are experiencing our needs as met or unmet. Identifying feelings is said to allow us to more easily connect with one another, and allowing ourselves to be vulnerable by expressing our feelings can help resolve conflicts.
- Needs: universal human needs, as distinct from particular strategies for meeting needs.
- Request: request for a specific action, free of demand. Requests are distinguished from demands in that one is open to hearing a response of "no" without this triggering an attempt to force the matter. If one makes a request and receives a "no" it is recommended not that one give up, but that one empathize with what is preventing the other person from saying "yes," before deciding how to continue the conversation. It is recommended that requests use clear, positive, concrete action language.
- Response: The receiving person has to respond clearly to the request:
- with a "yes"
- needs that prevent you from saying yes,
- and/or a counterproposal.
-
If they can’t find a solution agreeable to both of them, they nominate a colleague they both trust to act as a mediator. The mediator doesn’t impose a decision. Rather he or she supports the participants in coming to their own solution.
-
If mediation fails, a panel of topic-relevant colleagues is convened. The panel’s role, again, is to listen and help shape agreement. It cannot force a decision, but usually carries enough moral weight for matters to come to a conclusion.
-
In an ultimate step, the Top Level Circle Lead Link, can be called into the panel, to further reinforce the panel’s moral weight (but not to impose a solution).
- Three months probation period before signing anything, prolongation on mutual agreement
- 6 months cliff
- No stock purchase, but stock option for the ease of administration
- Master seniority, proportional shares based on ownership formula
Leave the office clean every day so it's a welcoming place for us and our guests.
- general cleaning (washing-up, vacuum-cleaning etc.) is outsourced to a cleaning lady, coming every Monday
- clean your desk everyday after yourself: no food, no dirty dishes
- clean common spaces / meeting desks after using it
- use dishwasher according to the magnet on the front (clean/dirty). If it is possible put your dirty dishes in the dishwasher. Take clean dishes out and put them to their place.
- start the dishwasher when it is full
- collect the trash selectively and take it down if it is full
- take the trash bag down if it is full and put in a new one
- do not disturb the meetings of others with loud noise
- make sure to clear the fridge every Friday, as the cleaning lady throws out old food from the fridge each Monday
- refill the fridge if it is out of water, beer etc.
- report to Office role if the office is out of something (beer, water etc.)
- the last one leaving the office has to close all the windows, alarm the office and lock the external doors
- Authorize at least two people to take your packages. Us the below, official form: https://www.posta.hu/static/internet/download/Meghatalmazas_nyomtatvany_20141021.pdf
No one can use the petty cash without permission from the Finance and Controlling role. Preferably, use Splitwise.
- Share the door code with your guests when you invite them to help us focus and reduce office noise.
- tea
- coffee
- beer
- wine
- sparkling water aka szóda
- fruit
- yogurt
- cereals
- 'szörp'
The company covers the flight cost of the relocating Partners.